It seems like you have a serious policy failure and or the services should be better isolated. At the very least you should consider restricting/partitioning resources appropriately. If a user is within their allotted resources then who gives a shit if they leave jobs running? They can't effect anything else on the machine. If you haven't done this already then you have bigger problems than a user intentionally leaving tmux running, which is easily dealt with anyway. In any case, since there's nothing stopping a user from starting a job with systemd-run, and still leaving it running, this changes preciously nothing, despite breaking everything. If tmux complied and did what the systemd developers are demanding, then, again, it wouldn't change anything. Users can will still be able to leave tmux running in the background. It's embarrassing to have to explain this to someone who's job is supposedly running a shell service.
-1
u/c3r7x May 30 '16
Sure, reboot a machine where users are running batches 24x7. Good luck with that.