bug#41123: shepherd exits for no good reason

[Ludovic Courtès]

Hi,

Mathieu Othacehe <address@hidden> skribis:

>> May  7 09:36:52 localhost shepherd[1]: Exiting shepherd... 
>> May  7 09:36:52 localhost shepherd[1]: Service xorg-server has been stopped. 
>> May  7 09:36:52 localhost shepherd[1]: Service console-font-tty2 has been 
>> stopped. 
>> May  7 09:36:52 localhost shepherd[1]: Service term-tty2 has been stopped. 
>> May  7 09:36:52 localhost shepherd[1]: Service upower-daemon has been 
>> stopped. 
>> May  7 09:36:52 localhost shepherd[1]: Service elogind has been stopped. 
>> May  7 09:36:52 localhost ntpd[482]: ntpd exiting on signal 15 (Terminated)
>> May  7 09:36:52 localhost syslogd: exiting on signal 15
>>
>> The end result was a kernel panic with exitcode=0x100 (meaning exited
>> with 1).
>>
>> It looks as though one had run ‘herd stop root’.
>
> It could be related to this bug[1]. The problem is that on 0.8.0 a
> process restart can cause a root-service stop.
>
> On your log, I can't see a process being restarted, so it might also be
> unrelated.

It looks very much the same though: it’s stopping itself, which most
likely happens as a result of killing itself.  I’ve merged them, we’ll
see!

Ludo’.