Re: systemd 230 change - KillUserProcesses defaults to yes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/01/2016 04:43 AM, 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".

What about a default shell alias for those commands, Fedora already add a few aliases, not sure if there are packaging guidelines for that.

The alias script could check if lingering is enabled and warn the user about it.

The only problem is when people call tmux/screen from an script, I don't do it, I start them by hand on a terminal when I want it. Probably more people use them as part of a script.


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.

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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux