http://bugzilla.opensuse.org/show_bug.cgi?id=1021969 http://bugzilla.opensuse.org/show_bug.cgi?id=1021969#c1 Andreas Stieger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |astieger@suse.com --- Comment #1 from Andreas Stieger --- Why? We verified that the systemd %post triggers the required reload to apply the change in behavior. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021969 http://bugzilla.opensuse.org/show_bug.cgi?id=1021969#c4 Tony Mechelynck changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(antoine.mechelync | |k@gmail.com) | --- Comment #4 from Tony Mechelynck --- After running zypper up for that patch, it advises to run "zypper ps -s" because some processes are using deleted files. Following this advice shows that the systemd (and systemd-journald) executables currently running are deleted. AFAIK, the only case where updating systemd would not require a reboot in order to execute the newly installed systemd executable is if, at that moment, the system were running under Sys V init instead; however, the same patch includes an update to systemd-sysvinit too, so a reboot would also be needed then, in order to execute the newly installed sysvinit. You might call this a question of principle: without rebooting, the newly installed systemd (or sysvinit) executable would never be run AFAIK. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021969 http://bugzilla.opensuse.org/show_bug.cgi?id=1021969#c6 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fbui@suse.com) | --- Comment #6 from Franck Bui --- (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. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021969 http://bugzilla.opensuse.org/show_bug.cgi?id=1021969#c8 Tony Mechelynck changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |FIXED Flags| |needinfo?(fbui@suse.com) --- Comment #8 from Tony Mechelynck --- (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.

http://bugzilla.opensuse.org/show_bug.cgi?id=1021969 http://bugzilla.opensuse.org/show_bug.cgi?id=1021969#c10 Tony Mechelynck changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |WONTFIX Flags| |needinfo?(fbui@suse.com) --- Comment #10 from Tony Mechelynck --- I notice that there are two systemd processes running on my system: one of them has PID 1, and the other has PPID 1 (and of course a different PID). To restart them both, experiment shows that both these commands are needed: systemctl daemon-reexec systemctl --user daemon-reexec Maybe the upgrade procedure does the former but not the latter? Also, the change from WONTFIX to FIXED, which the bug history says I made, was not intentional. Either inattention, or some Bugzilla quirk. -- You are receiving this mail because: You are on the CC list for the bug.