Subject: bug#44669: Shepherd loses track of elogind

From: Ludovic Courtès <[email-masked]>
Date: Mon, 16 Nov 2020 15:58:38 +0100

Hi Marius,

Marius Bakke <[email-masked]> skribis:

> On a newly-installed i7 system, Shepherd believes that the "elogind"
> service is not running.  Yet there is an 'elogind-daemon' process,
> spawned by PID 1, preventing subsequent "herd start elogind" invocations
> from succeeding.

Could you show the relevant /var/log/messages bits?  That should show
when/why elogind stopped.

That’s from 1.2.0rc1?

Thanks,
Ludo’.