Some systemd advocates say the critics are just upset at change. I don't dislike change in general, but changing defaults out from under me? Defaults like this? That irks me. I lost a several tmux sessions before I realized what was happening. I thought I was doing something wrong because SystemD violated my expectations so severely.
The whole point is for the administrators to be able to avoid users running long-running processes on shared systems (e.g. university systems).
Of course not. But I do want to have the nohup software they have running to keep running when they log out.
> The whole point is for the administrators to be able to avoid users running long-running processes on shared systems (e.g. university systems).
Right, which is why it should be possible to do this. The issue is that the default behavior has changed from honoring nohup to not honoring nohup. Defaulting to honoring nohup is what's expected, and is reasonable.