8 Feb
2013
8 Feb
'13
2:16 p.m.
Guillaume Rousse <guillomovitch@gmail.com> writes:
There was a packaging error, indeed, but I'm not sure it was the only cause of the problem here, as I was able to reproduce the issue even with a correct state directory. I guess any start failure will trigger this issue, given systemd socket activation mechanism.
Yep, any start failiure will trigger it, indeed. There's not much I can do about that on the syslog-ng side I think. If there is, do let me know, though :) Come to think of it.. supporting sd_notify() might be a solution here, but I have to read up on what that exactly buys us. -- |8]