On Fri, 24 Apr 2020 08:06:53 -0400,
Rich Freeman wrote:
>
> On Fri, Apr 24, 2020 at 6:31 AM Neil Bothwick <[email protected]> wrote:
> >
> > On Fri, 24 Apr 2020 10:41:24 +0200, Michele Alzetta wrote:
> >
> > > ... I just hope the remote system isn't running systemd, if so, you
> > > have to do some additional tweaking before screen or tmux work. I know
> > > someone who was bitten hard by this. Apparently systemd by default
> > > closes all running processes of a user on logout.
> >
> > I've never seen this and I regularly update systemd computers using tmux.
>
> It is a configurable option. I can't imagine that many distros enable
> it by default since it is likely to be shocking to anybody who
> actually knows how to use screen, and pointless for anybody who does
> not. :)
>
> To enable it set KillUserProcesses=yes in /etc/systemd/logind.conf
>
> If you do use it there are ways to make exceptions for particular processes.
>
> I can certainly see how it is a useful feature to have available in
> specific contexts, but obviously most people will want to have it
> turned off.
Or simplest of all use the at command possibly using script as the
command line and some way to answer the do you want to emerge
... question.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
[email protected]
