News for hackers. Stuff that matters.
Re:Systemd as tragedy by xyzzyz on Tuesday January 29, 2019 @01:03AM (#19024150)
There's a benefit, you're just not seeing it. Again, do you think that the systemd developers decided to implement it just to screw with people? As I said, there's a specific trade-off involved here.

I agree that it might not be the most desirable default, but if that's the case, then the guilt also falls on the distribution maintainers, who either ignored the big bold letters in the changelog, or didn't bother to test the everyone's standard workflows before pushing to stable.

Re:Systemd as tragedy by inferiorhuman on Tuesday January 29, 2019 @01:08AM (#19024174)
> Again, do you think that the systemd developers decided to implement it just to screw with people?

Based on Lennart's behavior, yes I do.

Re:Systemd as tragedy by michaelmrose on Tuesday January 29, 2019 @03:31AM (#19024730)
Instead of pretending the benefit is so obvious it doesn't require you to discuss it perhaps you could explain it.
Re:Systemd as tragedy by dvfjsdhgfv on Tuesday January 29, 2019 @03:59AM (#19024854)
Not the parent nor Systemd developers, but apparently they think it's the only way to make sure the user's session is cleaned up.

But frankly, 100% people would be fine with it if the default was left at no instead of changing it to yes. It's all about giving users a choice when a new feature is introduced, something Systemd developers understand only partially.

Re:Systemd as tragedy by zorpner on Tuesday January 29, 2019 @01:27AM (#19024252)
There's a benefit, you're just not seeing it.

Not to appeal to self-authority, but I have been maintaining production Linux systems in large-scale environments since the late 90s. If there were a benefit that outweighed the unnecessary breaking changes, I would see it, even if I didn't appreciate it. There isn't.

You should stop and think before you assume that other people are incompetent, both because it would make you a better interlocutor, and as a bonus it wouldn't violate HN's principle of charity.

Re:Systemd as tragedy by xyzzyz on Tuesday January 29, 2019 @12:17PM (#19028017)
The benefit is, of course, clean up of orphan defunct processes. One might argue if this is outweighing the drawback of the change (it might not, but that’s what some distro maintainers chose to enable), but you shouldn’t suggest that they just broke you for no purpose, instead, you should stop and think before you assume that other people are incompetent, both because it would make you a better interlocutor, and as a bonus it wouldn't violate HN's principle of charity.
Re:Systemd as tragedy by zorpner on Tuesday January 29, 2019 @07:34PM (#19031426)
Your copy/paste doesn't apply to my comment, since I didn't assume you were incompetent, just that you'd made an overaggressive claim you didn't care to back up.

Of course, a defense of systemd's comically broken reaping behavior removes all necessity for assumption in this case. sysvinit at least consistently reaps on SIGCHLD -- systemd randomly reorders into the sd-event API and then does something random based on the order receipt.

Re:Systemd as tragedy by xyzzyz on Tuesday January 29, 2019 @08:13PM (#19031663)
> Your copy/paste doesn't apply to my comment, since I didn't assume you were incompetent, just that you'd made an overaggressive claim you didn't care to back up.

Sorry, I assumed you're competent enough to figure it out, or at least look at the original sources where authors of the change explicitly explain the reason why they do it. Of course, since you assumed that they are incompetent, you didn't bother to do so, instead, completely uncharitably assumed that there's zero benefit for that.

Re:Systemd as tragedy by andrewshadura on Tuesday January 29, 2019 @02:24AM (#19024466)
I'm sorry to bring bad news, but there's indeed a benefit, you just don't see it.
Re:Systemd as tragedy by zorpner on Tuesday January 29, 2019 @02:50AM (#19024568)
Surely it can be articulated, then.
Re:Systemd as tragedy by andrewshadura on Wednesday January 30, 2019 @06:07AM (#19034162)
It was, many times, you can just google and educate yourself.