pool/systemd
SHA256
2
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

- Don't reexecute user manager instances on package update yet

Browse Source 
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
This commit is contained in:
Franck Bui 2021-09-08 17:13:42 +00:00 committed by Git OBS Bridge
parent e2348dd9f0
commit 588927516a
4 changed files with 34 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
systemd-mini.changes
View File

@ -1,3 +1,12 @@
-------------------------------------------------------------------
Wed Sep 8 17:01:58 UTC 2021 - Franck Bui <fbui@suse.com>
- 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 <fbui@suse.com> Wed Sep 8 13:21:34 UTC 2021 - Franck Bui <fbui@suse.com>

9
systemd-mini.spec
View File

@ -950,7 +950,14 @@ systemctl daemon-reexec || :
# user service is started before the user manager get reexecuted. But # user service is started before the user manager get reexecuted. But
# this case is very unlikely especially since we don't restart any # this case is very unlikely especially since we don't restart any
# user service for now on. # 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 %journal_catalog_update
%tmpfiles_create %tmpfiles_create

9
systemd.changes
View File

@ -1,3 +1,12 @@
-------------------------------------------------------------------
Wed Sep 8 17:01:58 UTC 2021 - Franck Bui <fbui@suse.com>
- 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 <fbui@suse.com> Wed Sep 8 13:21:34 UTC 2021 - Franck Bui <fbui@suse.com>

9
systemd.spec
View File

@ -948,7 +948,14 @@ systemctl daemon-reexec || :
# user service is started before the user manager get reexecuted. But # user service is started before the user manager get reexecuted. But
# this case is very unlikely especially since we don't restart any # this case is very unlikely especially since we don't restart any
# user service for now on. # 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 %journal_catalog_update
%tmpfiles_create %tmpfiles_create