Re: Re: [gentoo-user] Cannot shutdown or reboot because of logind disconnection

[Rich Freeman <rich0@gentoo.org>]

On Sat, Sep 17, 2022 at 8:21 AM johnstrass <johnstrass@163.com> wrote:
>
>
> Why is the logind so fragile?

Have you checked your logs.  I'm guessing that the kernel OOM killer
is killing it, and it is kind of hard for a process to not die when
the kernel kills it.

> Why cannot it be  brought up again after the memeory become available again?

I suspect it probably could be - probably not a failure mode upstream
has paid much attention to.  If the OOM killer is loose on your
system, general breakage is to be expected.  It is actually surprising
though that it didn't go after gcc itself.  I'd check the logs.

You probably could tweak the unit setting so that logind is less
likely to get prioritized.  Then it might go after something less
essential like sshd or postfix.  :)

Also possible that it isn't logind itself but something else it uses
for IPC.  Haven't looked into the gory details of how it works.

I'm guessing systemd could be coaxed to shut down without it.  It
might actually do that on its own if you give it time, but I haven't
checked the settings.

-- 
Rich