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 use 'systemd-run --scope --user' instead.
On Sat, Oct 19, 2019 at 6:51 PM Reco <recovery...@enotuniq.net> wrote: > 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 service. > 2) (Ab)use systemd-run. > 3) Replace GNOME with some other DE that respects your long-running > processes. > > Reco > >
