| 1 |
On Fri, 24 Apr 2020 08:06:53 -0400, Rich Freeman wrote: |
| 2 |
|
| 3 |
> > > ... I just hope the remote system isn't running systemd, if so, you |
| 4 |
> > > have to do some additional tweaking before screen or tmux work. I |
| 5 |
> > > know someone who was bitten hard by this. Apparently systemd by |
| 6 |
> > > default closes all running processes of a user on logout. |
| 7 |
> > |
| 8 |
> > I've never seen this and I regularly update systemd computers using |
| 9 |
> > tmux. |
| 10 |
> |
| 11 |
> It is a configurable option. I can't imagine that many distros enable |
| 12 |
> it by default since it is likely to be shocking to anybody who |
| 13 |
> actually knows how to use screen, and pointless for anybody who does |
| 14 |
> not. :) |
| 15 |
> |
| 16 |
> To enable it set KillUserProcesses=yes in /etc/systemd/logind.conf |
| 17 |
|
| 18 |
Thanks for that, now I know which man page to check it all makes sense. |
| 19 |
The man page does say that it defaults to off. I agree that there |
| 20 |
wouldn't be much point in a general purpose distro overriding this default |
| 21 |
but I can see times it would be useful. |
| 22 |
|
| 23 |
> If you do use it there are ways to make exceptions for particular |
| 24 |
> processes. |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Neil Bothwick |
| 29 |
|
| 30 |
WYTYSYDG - What you thought you saw, you didn't get. |
Archives