Re:I've now disabled systemd-oomd on my Fedora desktops
by josephcsible on Wednesday December 07, 2022 @06:18PM
(#33901793)
> 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?
Re:I've now disabled systemd-oomd on my Fedora desktops
by kaba0 on Wednesday December 07, 2022 @07:28PM
(#33902438)
That’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.
Re:I've now disabled systemd-oomd on my Fedora desktops
by josephcsible on Wednesday December 07, 2022 @09:56PM
(#33903556)
How is this random systemd convention better than a random UNIX convention though?
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)