On Fri, May 27, 2016 at 5:51 AM, Dominique Martinet <dominique.marti...@cea.fr> wrote: > Hi, > > Just noticed this change on rawhide... > https://github.com/systemd/systemd/blob/master/NEWS#L29 > * systemd-logind will now by default terminate user processes that are > part of the user session scope unit (session-XX.scope) when the user > logs out. This behavior is controlled by the KillUserProcesses= > setting in logind.conf, and the previous default of "no" is now > changed to "yes". This means that user sessions will be properly > cleaned up after, but additional steps are necessary to allow > intentionally long-running processes to survive logout. > > While the user is logged in at least once, user@.service is running, > and any service that should survive the end of any individual login > session can be started at a user service or scope using systemd-run. > systemd-run(1) man page has been extended with an example which shows > how to run screen in a scope unit underneath user@.service. The same > command works for tmux. > > After the user logs out of all sessions, user@.service will be > terminated too, by default, unless the user has "lingering" enabled. > To effectively allow users to run long-term tasks even if they are > logged out, lingering must be enabled for them. See loginctl(1) for > details. The default polkit policy was modified to allow users to > set lingering for themselves without authentication. > > Previous defaults can be restored at compile time by the > --without-kill-user-processes option to "configure". > > > So, now, I've read this and I could possibly remember to use systemd-run > or to set myself as lingering... Except that I don't want to have to go > through the pain of remembering to either change the system config on > all my servers or always starting stuff with systemd-run if it's a bit > long and I think I might want to ^Z/bg/disown it to let it finish.
This breaks the storage of ssh-agent credentials for te one-time enabling of SSH credentials for access on running hosts. Gods alone know what else it will break. -- devel mailing list devel@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
