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.
