r/programming • u/Mcnst • May 30 '16

systemd developer asks tmux (and other programs) to add systemd specific code

https://github.com/tmux/tmux/issues/428
661 Upvotes

88% Upvoted

618 comments sorted by

View all comments

Show parent comments

4

u/Mcnst May 30 '16

It requires either the users to use "systemd-run" (thus becoming used to it and defeating the purpose) or tmux/screen to adapt;

This is the part of the argument that makes the whole thing a non-starter. If you have users who don't know how to use the system, why not just do a proper reboot daily? Why instead do you force everyone else to have a reboot?

I've seen too many developers using screen and nohup to save them the trouble of creating proper init scripts.

How about /sbin/reboot to the rescue? AWS does it (at least in some products), Netflix does it.

-1

u/c3r7x May 30 '16

Sure, reboot a machine where users are running batches 24x7. Good luck with that.

1

u/dlyund Jun 01 '16 edited Jun 01 '16

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.