Mailinglist Archive: opensuse-bugs (4258 mails)

< Previous Next >
[Bug 1021969] Any patch applying to both systemd and systemd-sysvinit should have the reboot flag
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 27 Jan 2017 19:24:21 +0000
  • Message-id: <bug-1021969-21960-rUMsKyYwph@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1021969
http://bugzilla.opensuse.org/show_bug.cgi?id=1021969#c8

Tony Mechelynck <antoine.mechelynck@xxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|WONTFIX |FIXED
Flags| |needinfo?(fbui@xxxxxxxx)

--- Comment #8 from Tony Mechelynck <antoine.mechelynck@xxxxxxxxx> ---
(In reply to Franck Bui from comment #6)
(In reply to Tony Mechelynck from comment #4)

You might call this a question of principle: without rebooting, the newly
installed systemd (or sysvinit) executable would never be run AFAIK.

Please have look at the systemctl man page, specially the "daemon-reexec"
command.

Now I just did. What it doesn't explain is why, after "zypper up -t patch -t
package" finishes installing the upgrade to systemd etc. and the bash prompt
reappears, running "zypper ps" shows the systemd and systemd-journald
executables with the mention "(deleted)". If the daemon had actually reexecuted
itself (and not just done a long branch to its own entry point) the executable
now being run ought to have been the upgraded one, not the old, deleted, one.
So are you sure "systemctl daemon-reexec" is indeed executed as part of the
"zypper up" run?

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References