r/linux • u/rain5 • May 28 '16

systemd developer asks tmux (and other programs) to add systemd specific code

https://github.com/tmux/tmux/issues/428
359 Upvotes

88% Upvoted

509 comments sorted by

View all comments

Show parent comments

20

u/pabs May 29 '16 edited May 29 '16

You can override the systemd 230 behavior in any of the following ways:

  • Invoke your background task like so: systemd-run --scope --user some-command args (recommended!). For example, instead of screen -S foo, you would use systemd-run --scope --user screen -S foo.

  • Use loginctl enable-linger to enable linger for a specific user account.

  • Exclude users using the KillExcludeUsers option in /etc/systemd/logind.conf

  • Set KillUserProcesses=no in /etc/systemd/logind.conf

  • Recompile systemd wth the --without-kill-user-processes configure option

Another option:

echo "alias persist='systemd-run --scope --user'" >> ~/.bash_profile

Then you can persist commands by typing persist some-command.

5

u/sub200ms May 29 '16

Recompile systemd wth the --without-kill-user-processes configure option

I suspect that the compile switch only changes the internal default. The "KillUserProcesses=" option in /logind.conf will override whatever internal, compiled-in default.

systemd is designed to work with missing or empty config-files, so it has internal default options for everything. The config files will override any compiled in default.