From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] systemd: Reexec systemd after update.
Date: Sun, 21 Jun 2015 22:11:49 +0200 [thread overview]
Message-ID: <1434917509.16390.1.camel@ipfire.org> (raw)
In-Reply-To: <1434916976-21899-1-git-send-email-stefan.schantl@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
On Sun, 2015-06-21 at 22:02 +0200, Stefan Schantl wrote:
> Reexec the systemd init daemon after update from now. This will prevent
> from leaving the system in an undefined / unuseable status.
>
> Fixes #10820.
>
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> systemd/systemd.nm | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/systemd/systemd.nm b/systemd/systemd.nm
> index 3ed1b5b..123d48f 100644
> --- a/systemd/systemd.nm
> +++ b/systemd/systemd.nm
> @@ -5,7 +5,7 @@
>
> name = systemd
> version = 215
> -release = 1
> +release = 1.1
Why 1.1 and not 2?
>
> maintainer = Stefan Schantl <stefan.schantl(a)ipfire.org>
> groups = System/Base
> @@ -226,6 +226,9 @@ packages
> end
>
> script postup
> + # Re-exec systemd after update.
> + /usr/bin/systemctl daemon-reexe
Rejected as there is clearly a 'c' missing.
> +
> # Restart login service after update
> /usr/bin/systemctl daemon-reload >/dev/null 2>&1 || :
> /usr/bin/systemctl try-restart systemd-logind.service >/dev/null 2>&1 || :
Do we need the daemon-reload command after re-exec?
-Michael
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-21 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-21 20:02 Stefan Schantl
2015-06-21 20:11 ` Michael Tremer [this message]
2015-06-21 20:23 ` Stefan Schantl
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=1434917509.16390.1.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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