From: Henning Schild <henning.schild@siemens.com>
To: isar-users@googlegroups.com
Cc: Henning Schild <henning.schild@siemens.com>
Subject: [PATCH] sshd-regen-keys: fix systemd service
Date: Mon, 9 Mar 2020 14:03:15 +0100 [thread overview]
Message-ID: <20200309130315.11031-1-henning.schild@siemens.com> (raw)
From: Henning Schild <henning.schild@siemens.com>
In rare cases the service can leave sshd without keys. Turns out that
the service file to run "before" was wrong.
Signed-off-by: Henning Schild <henning.schild@siemens.com>
---
.../sshd-regen-keys/files/sshd-regen-keys.service | 2 +-
.../{sshd-regen-keys_0.2.bb => sshd-regen-keys_0.3.bb} | 0
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/sshd-regen-keys/{sshd-regen-keys_0.2.bb => sshd-regen-keys_0.3.bb} (100%)
diff --git a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
index a05e1a98..f50d34c8 100644
--- a/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
+++ b/meta/recipes-support/sshd-regen-keys/files/sshd-regen-keys.service
@@ -3,7 +3,7 @@ Description=Regenerate sshd host keys
DefaultDependencies=no
Conflicts=shutdown.target
After=systemd-remount-fs.service
-Before=shutdown.target sshd.service
+Before=shutdown.target ssh.service
ConditionPathIsReadWrite=/etc
[Service]
diff --git a/meta/recipes-support/sshd-regen-keys/sshd-regen-keys_0.2.bb b/meta/recipes-support/sshd-regen-keys/sshd-regen-keys_0.3.bb
similarity index 100%
rename from meta/recipes-support/sshd-regen-keys/sshd-regen-keys_0.2.bb
rename to meta/recipes-support/sshd-regen-keys/sshd-regen-keys_0.3.bb
--
2.24.1
next reply other threads:[~2020-03-09 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 13:03 Henning Schild [this message]
2020-03-10 22:11 ` Henning Schild
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=20200309130315.11031-1-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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