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: 1, Insightful) by Anonymous Coward on Monday May 30 2016, @07:38PM
Oh sure, SystemD totally sucks. (That's settled science at this point.)
But guess what, so do these other great innovations (mostly brought to you, it would seem, by RedHat):
xinetd
policykit
gnome
anaconda
dbus
avahi
SELinux
Apparmor
dhcpcd (or dhclient, depending on your perspective)
...and probably about 300 other "improvements" I can't think of right now.
The battle for Linux is long over. SystemD is just the final nailing of the coffin.
(Score: 0) by Anonymous Coward on Monday May 30 2016, @11:51PM
You forgot all the "kits." Total amateur hour. Gimme a break, are all Linux devs in eighth grade?
(Score: 0) by Anonymous Coward on Tuesday May 31 2016, @02:17AM
(Score: 0) by Anonymous Coward on Tuesday May 31 2016, @01:01PM
SELinux was not originally Red Hat's, but the NSA's creature. It seems that the NSA didn't take that opportunity to hide a back door in there somewhere though.
OH YES because there's no way they'd want try--or even be able--to do that.
Return to your homes, there is nothing to see here. Just another spy organization writing free software because it's fun
(Score: 0) by Anonymous Coward on Wednesday June 01 2016, @01:23PM
Originally done by interns to test out a hardening technique they felt could make linux 'military grade'. I forget if they had already had another unix version of it prior to that, but it certainly wasn't an 'NSA' project in the traditional sense.