bug#30939: shepherd: detailed output should be placed into well-known location and not tty

[Clément Lassieur]

Ludovic Courtès <address@hidden> writes:

> Hello,
>
> ng0 <address@hidden> skribis:
>
>> Sometimes I succeed building a system generation with an OpenSMTPD 
>> config-file
>> which has syntax error that aren't picked up at configure time. When I 
>> reboot,
>> not being aware of this, I have to switch to tty to read the reasons why it
>> crashed.
>> Because this is a desktop system, I have to start the service again to see
>> the error output directly from the daemon.
>
> I think shepherd could capture stdout/stderr of the processes it starts
> and make it available, in a way similar in spirit to what ‘journalctl’
> does.  That would allow you to see the output of the daemon that failed.

That would be great!

> That’s the only solution I can think of.  Of course we don’t have to do
> that if the daemon writes error messages to syslog, but not all of them do.
>
> Thanks,
> Ludo’.