4 ms·
> This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out. Even if the change is a genuine impr
by Someone 2mo ago
> This is why i dislike systemd. Things not working the way I expect means I have to do more work to figure something out.
Even if the change is a genuine improvement?
- dosisking 2mo agoHow can the change be a genuine improvement, if it does something unexpected that needs to be figured out?
- graemep 2mo agoThis is not a genuine improvement: > One of the features of systemd that is most controversial is the option to kill user processes when the user logs out. That initially killed screen/tmux/nohup processes too. Killing processes that the user clearly did not want killed is a regression. Reading the rest of article it seems that its fixed but made things a lot more complicated than "unless you deliberately start things so that they keep running when you logout they will be killed when you logout". Am I wrong?
- preg_match 2mo agoI don't think it's a regression at all. It's been standard advice for decades that logout-login wipes user processes for updates, therefore you don't need to restart. I'd argue the opposite is true: linger is surprising, and I turn it off.
- graemep 2mo agoI I start a process with nohup and logout I clearly want it to keep running. That is the entire point of nohup. If that process is killed when I logout then that is a regression. I do not understand what this has to do with udaptes.
- egorfine 2mo agoYes. Improvement or not, a thing not working the way one expects means one has to do more work to figure something out. And in case of pid1, this is never a time spent productively. I'm all for improvements and I love updates of software, but what systemd usually does is ideology and destruction in the name of "new". Like, we have had cron perfectly working for _decades_ until one man told us we were all wrong on that.