From: Florian Bezdeka <florian.bezdeka@siemens.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, henning.schild@siemens.com,
Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: [PATCH v2 0/2] sshd-regen-keys: Fix boot hang on low end hardware
Date: Fri, 15 Oct 2021 10:06:36 +0200 [thread overview]
Message-ID: <20211015080638.12765-1-florian.bezdeka@siemens.com> (raw)
Hi,
when booting a Debian 11 based ISAR image with sshd-regen-keys
enabled on low end systems it could happen that the first boot
took too long so that the configured timeout for serial console
systemd units was hit.
It turned out that running sshd-regen-keys in parallel to
systemd-random-seed is not the best idea. Patch one fixes that by
moving the start of sshd-regen-keys after the point in time where
systemd-random-seed completed.
Patch two fixes two warnings that were discovered on Debian 11. I
tested that with Debian 10 as well. Worked as expected.
Best regards,
Florian
---
Changes since v1:
- Rebased on current next
Florian Bezdeka (2):
sshd-regen-keys: Start key generation after entropy seed
sshd-regen-keys: Fix some systemd obsolete warnings about using syslog
.../sshd-regen-keys/files/sshd-regen-keys.service | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-15 8:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 8:06 Florian Bezdeka [this message]
2021-10-15 8:06 ` [PATCH v2 1/2] sshd-regen-keys: Start key generation after entropy seed Florian Bezdeka
2021-10-15 8:06 ` [PATCH v2 2/2] sshd-regen-keys: Fix some systemd obsolete warnings about using syslog Florian Bezdeka
2021-10-22 14:59 ` [PATCH v2 0/2] sshd-regen-keys: Fix boot hang on low end hardware Anton Mikanovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211015080638.12765-1-florian.bezdeka@siemens.com \
--to=florian.bezdeka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox