OK, I found the problem when trying to obtain the logs. I called s6-setuidgid to a user that hasn't had permissions to the folder. Stupid me.
I was expecting some logs in the catch all logger in /run/uncaught-logs/ but found nothing. Is this ok? Thank you On Tue, Mar 8, 2016 at 3:10 PM, Laurent Bercot <[email protected]> wrote: > On 08/03/2016 14:37, Jan Olszak wrote: > >> s6-log crushes when the logdir isn't clean. For example: after reboot >> s6-log's logdir contains files from the previous run but instead of >> appending to the logs s6-log quits. >> > > Sounds weird. Normally s6-log picks up where it left off. > > Do you have the precise error message ? An strace output of s6-log would > be nice too. > > -- > Laurent >
