severity 395056 normal thanks On Tue, Oct 24, 2006 at 06:47:11PM +0200, Christoph Biedl wrote: > Package: smokeping > Version: 2.0.9-1 > Severity: wishlist > > After an upgrade from sarge I noted smokeping was not running, even > after manual restart. Further investigation revealed that the problem is > actually a problem with a dying syslog-ng (#384021). However, smokeping > dies if it cannot write to /dev/log which happens if there's no syslog > daemon running. > > And: This message is not visible. > > Looking into the sources I find this problem is not specific for > smokeping, it's perl's syslog call. Hence just a wish: Please place a > warning in the manual page or the default config file that smokeping > requires a running syslog daemon for operation. > > Alternatively, catching that error and continue operation was a nice > thing to have.
Hi, and thanks for your report. This is easy to fix in the initialization code, and I'll certainly add a check for it. However, I'm not sure what to do if syslog() fails after the startup daemonization. As all the filehandles have been closed, there's nowhere to log an error, but continuing the operation without any logging doesn't seem a good choice either. Oh well, I guess it's best to just continue running in that case. When syslogd comes back, the logging should work again. 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. Cc'ing Tobi Oetiker, the other upstream author. Cheers, -- Niko Tyni [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
