On Wed, 2016-06-01 at 04:43 -0400, Matthew Miller wrote: > On Sun, May 29, 2016 at 06:51:20PM -0600, Chris Murphy wrote: > > > > So there's tmux, screen, curl, wget, and probably quite a few > > others > > that don't necessarily get daemonized that are probably affected. > I would really like to see a solution whereby tmux and screen _just > work_ without any required changes to user behavior. They're > basically > commands which _indicate_ "I want a new session that persists". > > It seems fine to have some administrative option which prevents that, > but I think allowing that behavior should be the default. That way, > accidental lingering processes will be cleaned up, but people's > expectations around tmux/screen will still be met. Yeah - I think that making tmux/screen & co persistent makes sense regardless how the systemd default is set on Fedora in the end. That's really the only way to make stuff consistent for users once the persistence on/off switch consists. > > I liked the suggestion of having those programs become "scope" aware > (https://github.com/tmux/tmux/issues/428) but it looks like upstream > tmux at least is not keen on it. What can we do instead? > > -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
