On Sat, Jul 9, 2016 at 4:56 PM, Chris Murphy <lists(a)colorremedies.com>
wrote:
I think this needs to be rethought. The options right now are,
modify
an as yet unknown quantity of background programs so they aren't
killed on user logout; vs logout/restart/shutdown likely hanging for
90 seconds. It seems the work around would be to modify screen and
tmux, and then run all such background tasks in either screen or tmux.
But, that's kinda, wow... bit of a hammer.
A thought occurred to me: would it be possible to instead implement a
whitelist of *binaries* that are allowed to linger, rather than going
around patching everything? So for example rather than having to modify the
codebase of screen, we have a (sysadmin-modifiable) whitelist that says
/usr/bin/screen is allowed to linger? Perhaps this would be something
shipped by the screen package, so /usr/bin/screen is only whitelisted if
the package providing it installed.
Just an idea that I probably haven't fully thought through yet... it may
have even been something mentioned on the last thread. This just seems like
it might be a better approach than trying to patch an arbitrary number of
programs, though?
Ben Rosser