On Wed, 2016-08-10 at 16:26 +0200, Ruediger Meier wrote:
On Wednesday 10 August 2016, Martin Wilck wrote:
SIGHUP is sent immediately after SIGTERM,
Actually I get 3 signals within the same millisecond.
two would be expected, the 3rd one is perhaps a bug?
to avoid the long timeout you complain about.
It could also try all other kind of signals ... to increase the chance that the process will run into SIG_DFL ...
Please - treating the shell in a special way does make some sense.
BTW in future systemd-logind seems to be even more agressive: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394 Hope that openSUSE does not use this insane default.
KillUserProcesses is configurable in logind.conf. But traditionally, it's normal behaviour that background processes are killed when you log out.
No, my ssh-agent and many other progs have always run forever after starting them once.
Hm, is that really a good idea?
bash even seem to automatically "nohup" child processes (may depend on the used terminal).
Only if you "disown" them, to my understanding.
You have not understood that in systemd-230 especially nohup, screen and friends will be killed by default too ... the traditional way how to run background processes is not the default anymore ...
Indeed, I didn't read the debian bug far enough. Breaking nohup is sort of disconcerting, I agree. I wonder if "at" would be affected, too - using "at" has been my personal preferred method for long running jobs for a while. At first sight, it seems that "at" jobs end up in a different scope than the starting shell, so it's looking good thus far. Cheers Martin -- Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107 SUSELinux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org