News for hackers. Stuff that matters.
Re:Systemd as tragedy by MereInterest on Tuesday January 29, 2019 @10:45PM (#19032468)
I'm glad that it helped resolve your issue, though I still don't think it was an appropriate choice for a default. I tend to do most of my work on a remote server, using tmux and emacs daemon to pick up right where I left off in the case of a dropped connection. That systemd would terminate my process when I explicitly requested it not to be is very abnormal.
Re:Systemd as tragedy by pas on Wednesday January 30, 2019 @05:00AM (#19033884)
You haven't requested systemd, you started a user scope, and haven't started a service for what you need.

POSIX is nice, but rather lacking in certain aspects, such as security anf administration-friendliness. cgroups help with both, but people have to understand them and use them well.

Re:Systemd as tragedy by MereInterest on Wednesday January 30, 2019 @09:26AM (#19035233)
Handling and ignoring SIGHUP is the explicit way to indicate that a program should not be terminated. That systemd invented a new category and then ex post facto declared that everybody else was wrong for not using it is ridiculous. Systemd changing behavior such that I must "Simon says nohup" is completely asinine.