Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by cmn32480 on Monday May 30 2016, @06:44AM   Printer-friendly
from the fed-up-with-the-UNIX-take-over dept.

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.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0, Troll) by SemperOSS on Tuesday May 31 2016, @04:18PM

    by SemperOSS (5072) on Tuesday May 31 2016, @04:18PM (#353091)

    What peeves me in this discussion is the fact that most comments seem to ignore the fact that the offending behaviour of systemd can be turned off once and for all.

    If your system needs users to run background processes, disable the feature and let them.

    Easy as that.

    Why so much talk about a feature that can easily be disabled? I don't know about you, but every time I install a new Linux system — no matter what distro — I have to tweak it to my preferences and this would be such a tweak, if I actually used systemd. (I don't.)

    --
    I don't need a signature to draw attention to myself.
    Maybe I should add a sarcasm warning now and again?
    Starting Score:    1  point
    Moderation   -1  
       Troll=1, Total=1
    Extra 'Troll' Modifier   0  

    Total Score:   0  
  • (Score: 2) by termigator on Tuesday May 31 2016, @05:53PM

    by termigator (4271) on Tuesday May 31 2016, @05:53PM (#353135)

    For those that want the feature, then they can *explicitly* enable it. My complaint is changing the default behavior, a behavior that has existed for decades on *nix-type operating systems.