SoylentNews is people
SoylentNews
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 Tuesday May 31 2016, @04:31AM
You do not take into account that systemd is linux specific, and in a state of flux.
Why on earth should a free software dev complicate or fork his project to accommodate this? would you?
RH should fork it themselves instead of having unpaid volunteer time devoted to build castles on their sand.
Account abandoned.
(Score: 1) by SemperOSS on Tuesday May 31 2016, @03:52PM
In fact, I said that the developers should consider the possibility and either accepting it or rejecting it for inclusion in their project. The change may break some functionality but if you cannot live with that, disable the change, no reason to moan about it just because it is a pet hate project.
And just so you know, I have no connection to Poettering or systemd. In fact I try to avoid it as best I can, but please give the people some credit for not just forcing this change upon the unsuspecting world.
I don't need a signature to draw attention to myself.
Maybe I should add a sarcasm warning now and again?