News for hackers. Stuff that matters.
Re:Systemd, ten years later: a historical and technical retr... by Spivak on Monday May 04, 2020 @11:52AM (#23069465)
The functionality of implementing it yourself?

But that’s such a useless definition because then all software “provides nothing” since it’s implementation proves that you could have written it yourself.

logind is far more robust than any of the janky shell scripts I’ve seen over the years to accomplish this.

Re:Systemd, ten years later: a historical and technical retr... by TA0x0 on Monday May 04, 2020 @12:23PM (#23069954)
The functionality to gracefully end long running background processes has been a part of standard killall, pkill, etc. for quite some time.

Even then, yes, the functionality of using ps and kill together has existed for 20+ years. Those tools are already implemented, providing the functionality for decades.

In no universe is logind considered robust, and basic scripts from middling UNIX admins have provided this functionality for decades, untouched. Even the "janky" ones.

Re:Systemd, ten years later: a historical and technical retr... by cycloptic on Monday May 04, 2020 @01:29PM (#23070859)
See my comment below. These tools are fundamentally broken for this use case and have never provided the functionality needed. Bash scripts are not a process manager and it is incredibly wrong to try and make it work like one.
Re:Systemd, ten years later: a historical and technical retr... by TA0x0 on Tuesday May 05, 2020 @06:35PM (#23085933)
I responded to the comments below. These tools are not fundamentally broken, you're just ignorant in this space. They have always provided the functionality needed. Scripting can easily manage processes at a higher level, and it's basic functionality to make it work like that.