3 ms·
The point of a default is that it's what a setting should be if you don't go out of your way to change it. The default was on, and you're faulting the distro ma
by josephcsible 4y ago
The point of a default is that it's what a setting should be if you don't go out of your way to change it. The default was on, and you're faulting the distro maintainers for not changing it to off, when it should have just defaulted to off all along. (Or are you saying that it did default to off, and that the distro maintainers originally went out of their way to turn it back on? If so, that would surprise me, but I'd concede the point.)
Correct behavior is that a demonized process doesn't ever get killed just because another process in its original family tree dies.
- kaba0 4y ago> Correct behavior is that a demonized process doesn't ever get killed just because another process in its original family tree dies Who decides what is a demonized process, vs one that just froze and won’t respond to some random UNIX convention, that can’t even reliably signal its state (what is tmux when it is frozen?) So the solution is to explicitly specify that a given process wishes to live outside of the seat’s lifetime (either by specifying it as a service, which your earlier example ssh is on basically any distro, or by executing it as with systemd-run)
- josephcsible 4y ago> explicitly specify that a given process wishes to live outside of the seat’s lifetime Okay, so it does that now. But now how do you tell if it's frozen?
- kaba0 4y agoThat’s not really the point, but there are of course plenty of ways for that (output, watchdogs, etc). The point is that the OS does actually know “statically” that a given process is a daemon or not.
- josephcsible 4y agoHow is this random systemd convention better than a random UNIX convention though?
- kaba0 4y agoOne is decidable the other can have false positives.