Niko Tyni wrote... > Oh well, I guess it's best to just continue running in that case. When > syslogd comes back, the logging should work again.
Losing a log message is the smaller damage than losing smokeping
samples, perhaps even over a long time (until I notice). And the syslog
daemon might be unavailable for other reasons, for example it is just
being restarted the very same second and similar ugly things.
> This will be fixed in the next upstream version, and possibly in 2.0.9-2
> for etch if it looks like 2.0.10 is too late for etch. I'm raising the
> severity, as I think dying silently at startup is a real bug.
Thanks for a fast and kind reaction. Much appreciated.
Christoph
signature.asc
Description: Digital signature
