O changelog para o systemd (v230) diz:
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.
Portanto, este é o comportamento padrão. Ele também explica o que fazer para desfazer a alteração: logind.conf
, definir KillUserProcesses=
para no
(e
--without-kill-user-processes option
to configure
)
Mas o changelog também inclui um ...
While the user is logged in at least once,
[email protected]
is running, and any service that should survive the end of any individual login session can be started at a user service or scope usingsystemd-run
. systemd-run(1) man page has been extended with an example which shows how to run screen in a scope unit underneath[email protected]
. The same command works for tmux.
e
After the user logs out of all sessions, [email protected] 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.
Esse é mais importante, pois usa o padrão (kill'm all) com uma maneira de fornecer exceções: habilitar lingering
.
Mais algumas informações: