Option 2) worked. Thank you!
P.S rant: systemd is a constant pain, mostly because you are never prepared
for the changes. You are always wondering "why my scripts won't work
anymore". I am not happy that setsid doesn't work anymore, but what drives
me crazy is that nobody care to tell us we could
Hi.
On Sat, Oct 19, 2019 at 05:57:37PM +0200, Alejandro wrote:
> systemd-cgls shows they are running as part of
> gnome-terminal-server.service. I guess it explains how they are killed, but
> the main question remains: how do I stop such behavior?
Three choices:
1) Make your own user ser
systemd-cgls shows they are running as part of
gnome-terminal-server.service. I guess it explains how they are killed, but
the main question remains: how do I stop such behavior?
On Sat, Oct 19, 2019 at 11:48 AM Ansgar wrote:
> Camilo Alejandro Arboleda writes:
> > I'm running Debian testing wit
Camilo Alejandro Arboleda writes:
> I'm running Debian testing with Linux 5.2, Gnome 3.34.1 and systemd 242. At
> some point the last month systemd stopped honoring the
> "KillUserProcesses=no" setting in /etc/systemd/logind.conf. Now all
> processes get killed and googling shows nothing.
>
> Not s
4 matches
Mail list logo
