On Wed, Jun 1, 2016 at 10:28 AM, Tomasz Torcz <tomek(a)pipebreaker.pl> wrote:
I think that programs needing special treatment should use operating
system's facilities to communicate that. So tmux, screen, nohup should
really open a new session. It's unfortunate that tmux author is hostile
against that, but maybe a clean, compile-time optional patch would persuade
Anyway, I think some examples of ”how to inform systemd I'm a special
program not to reap” would be welcome. Does it need to be done through
D-Bus interaction with logind? Is using PAM sufficient/required?
(Nb. screen already uses PAM for some functionality).
As mentioned, this isn't just about screen, tmux, and nohup (or if there's
any other programs used in a similar context). *Any* command run with a
trailing & is commonly expected to survive logout, usually from remote
shells. Setting this as a default security policy without allowing that
standard behavior is going to be, at best, very surprising to a lot of
people, and documenting a new way to do the same thing isn't good enough.