On Fri, May 27, 2016 at 09:36:58AM -0500, Chris Adams wrote: > Once upon a time, Tom Hughes <tom@xxxxxxxxxx> said: > > On 27/05/16 15:25, Chris Adams wrote: > > >When you "clean up" by killing things that are designed to run after > > >logout, you are being over-zealous. It is incumbent upon you to fix > > >your cleanup methods to handle this case, not the thousands of users > > >to change their process to avoid your broken methods. > > > > But that's effectively calling for the impossible - if there has > > historically been no way for things to announce that they are > > expected to remain after exit then there's no way to magically > > identify them now. > > > > What would be good would be if screen and similar programs could > > learn to do the necessary magic automatically rather than having to > > be wrapped in systemd-run by the user. > > And that's what I'm suggesting. Before making this the default in > systemd, the systemd developers should come up with a way for processes > to make some type of notification, and then get patches into the common > things (screen and tmux at least, with freely-licensed example code for > others to use) to handle this. Only then should the default be changed. https://github.com/tmux/tmux/issues/428 -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
