Hi Konrad! I'm happy to read you could successfully make it work! It's strange that you had that issue though!
Cheers, Maxim On July 3, 2019 11:17:03 AM UTC, Konrad Hinsen <konrad.hin...@fastmail.net> wrote: >On 03/07/2019 10:12, Konrad Hinsen wrote: > >> All this suggests that perhaps the problem is not with syslogd, but >with >> shepherd wrongly concluding that syslogd failed. >> >> Looks like I will have to dig a bit more into shepherd :-( > >My hypothesis turned out to be correct: increasing the timeout was >sufficient to get syslogd working. > >Konrad.
