Bug#989317: systemd kill background processes after user logs out (#825394 regression)
Matt Corallo
dbsdsfdog at mattcorallo.com
Tue Jun 8 19:12:37 BST 2021
On 6/8/21 14:02, Michael Biebl wrote:
>> Is there an alternate way to run things that lxc should instead be recommending? In my interactions with the lxc folks
>> it seems this workaround is only relevant for Debian bullseye, so maybe other distros are patching systemd or changing
>> cgroup settings such that interacting with systemd isn't required.
>
> Are you sure? Which distros are that? Which exact version of that distro?
No, I'm not sure, but that was the response any time I mentioned systemd-run was immediately "I assume Debian bullseye
or something". Its possible it also impacts fedora and the Ubuntu folks just have some crazy workaround that doesn't
really make sense.
>> Similar to the discussion in 825394, having daemons spontaneously killed is incredibly surprising, maybe it makes
>> sense to enable-linger by default?
>
> That's not a good idea I think.
> Starting long running daemons from a user session is not the norm, I'd argue.
Would defer to you, I've never seen systemd-run used or mentioned anywhere outside of lxc.
> In any case, I'm not sure there remains anything to be done on the systemd side. Afaics, everything behaves as documented.
Sounds good.
More information about the Pkg-systemd-maintainers
mailing list