From 2b970d3e98f2cc0d7c1eb8d3bc8e7011dabe341563c1d62717320c488af8d4db Mon Sep 17 00:00:00 2001 From: Franck Bui Date: Wed, 8 Sep 2021 17:13:42 +0000 Subject: [PATCH] - Don't reexecute user manager instances on package update yet This can't be done until users have their user instance updated to the new version that supports reexecuting with SIGRTMIN+25 because this signal terminates the user managers for the previous versions. OBS-URL: https://build.opensuse.org/package/show/Base:System/systemd?expand=0&rev=1184 --- systemd-mini.changes | 9 +++++++++ systemd-mini.spec | 9 ++++++++- systemd.changes | 9 +++++++++ systemd.spec | 9 ++++++++- 4 files changed, 34 insertions(+), 2 deletions(-) diff --git a/systemd-mini.changes b/systemd-mini.changes index 9f5e048..d28a872 100644 --- a/systemd-mini.changes +++ b/systemd-mini.changes @@ -1,3 +1,12 @@ +------------------------------------------------------------------- +Wed Sep 8 17:01:58 UTC 2021 - Franck Bui + +- Don't reexecute user manager instances on package update yet + + This can't be done until users have their user instance updated to + the new version that supports reexecuting with SIGRTMIN+25 because + this signal terminates the user managers for the previous versions. + ------------------------------------------------------------------- Wed Sep 8 13:21:34 UTC 2021 - Franck Bui diff --git a/systemd-mini.spec b/systemd-mini.spec index 7e7f3b0..2de1c70 100644 --- a/systemd-mini.spec +++ b/systemd-mini.spec @@ -950,7 +950,14 @@ systemctl daemon-reexec || : # user service is started before the user manager get reexecuted. But # this case is very unlikely especially since we don't restart any # user service for now on. -systemctl kill --kill-who=main --signal=SIGRTMIN+25 "user@*.service" || : +# +# Before doing this, we unfortunately have to wait until users will +# reexec their user manager (by either rebooting or restarting their +# session) to a version that supports SIGRTMIN+25 otherwise sending +# the signal to an old version will kill the manager which means +# tearing down the user session. +# +# systemctl kill --kill-who=main --signal=SIGRTMIN+25 "user@*.service" || : %journal_catalog_update %tmpfiles_create diff --git a/systemd.changes b/systemd.changes index 9f5e048..d28a872 100644 --- a/systemd.changes +++ b/systemd.changes @@ -1,3 +1,12 @@ +------------------------------------------------------------------- +Wed Sep 8 17:01:58 UTC 2021 - Franck Bui + +- Don't reexecute user manager instances on package update yet + + This can't be done until users have their user instance updated to + the new version that supports reexecuting with SIGRTMIN+25 because + this signal terminates the user managers for the previous versions. + ------------------------------------------------------------------- Wed Sep 8 13:21:34 UTC 2021 - Franck Bui diff --git a/systemd.spec b/systemd.spec index 113a9a7..336ac69 100644 --- a/systemd.spec +++ b/systemd.spec @@ -948,7 +948,14 @@ systemctl daemon-reexec || : # user service is started before the user manager get reexecuted. But # this case is very unlikely especially since we don't restart any # user service for now on. -systemctl kill --kill-who=main --signal=SIGRTMIN+25 "user@*.service" || : +# +# Before doing this, we unfortunately have to wait until users will +# reexec their user manager (by either rebooting or restarting their +# session) to a version that supports SIGRTMIN+25 otherwise sending +# the signal to an old version will kill the manager which means +# tearing down the user session. +# +# systemctl kill --kill-who=main --signal=SIGRTMIN+25 "user@*.service" || : %journal_catalog_update %tmpfiles_create