The spreading of systemd continues, now actively pushed by themselves unto other projects, like tmux:
"With systemd 230 we switched to a default in which user processes started as part of a login session are terminated when the session exists (KillUserProcesses=yes).
[...] Unfortunately this means starting tmux in the usual way is not effective, because it will be killed upon logout."
It seems methods already in use (daemon, nohup) are not good for them, so handling of processes after logout has to change at their request and as how they say. They don't even engange into a discussion about the general issue, but just pop up with the "solution". And what's the "reason" all this started rolling? dbus & GNOME coders can't do a clean logout so it must be handled for them.
Just a "concidence" systemd came to the rescue and every other project like screen or wget will require changes too, or new shims like a nohup will need to be coded just in case you want to use with a non changed program. Users can probably burn all the now obsolete UNIX books. The systemd configuration becomes more like a fake option, as if you don't use it you run into the poorly programmed apps for the time being, and if they ever get fixed, the new policy has been forced into more targets.
Seen at lobsters 1 & 2 where some BSD people look pissed at best. Red Hat, please, just fork and do you own thing, leaving the rest of us in peace. Debian et al, wake up before RH signed RPMs become a hard dependency.
(Score: 2) by Bot on Monday May 30 2016, @03:18PM
Juan Pablo Daniel @jpdborgna 15h15 hours ago
"Systemd is pretty much a nonsensical nonsolution to an imaginary nonproblem." #systemd--
Nailed it.
Markus Lindenberg @moreentropy 18h18 hours ago
I'm tired of #systemd hate. It's not about how Unix was conceived 25 years ago but how I want my services to be run in 2016.
Great troll or average systemd user? Difficult to tell.
Account abandoned.
(Score: 1, Insightful) by Anonymous Coward on Monday May 30 2016, @03:56PM
Nobody would care if they had forked Linux and created Poetterix, just as Google did with Android. The problem is that this is forced on users who definitely don't want it. Offering more choice is good. Eliminating choice because "we know better" is bad.
(Score: 2) by Zz9zZ on Monday May 30 2016, @11:28PM
This is the rationale that seems to be beyond the sysd supporters... Leave the user with choice!
~Tilting at windmills~
(Score: 1, Informative) by Anonymous Coward on Monday May 30 2016, @06:44PM
1) For years, many people had to fix audio on Linux by removing Pulse Audio.
2) My instant messenger did not work because avahi-daemon interfered with DNS on the corporate network, which happened to use .local. I turned that service off and things just worked.
3) After rebooting, my Ethernet adapter would not acquire an address. I turned NM_CONTROLLED to no, and it just worked.
All 3 of these issues came from one person's software design. Excluding obscure hardware support, MySQL, and these 3 issues, my Linux experience would be very pleasant. systemd is clearly more defective by design then all 3 of these put together, so putting it on my system is literally insane (doing the same thing over and over again and expecting different results).