[syslog-ng] OT: why does writes to /dev/log block?

[Jason Haar]

Balazs Scheidler wrote:

>Basically, this is how it was designed to work. The syslog() call in
>libc uses a blocking call to send messages to syslogd, if the socket is
>opened (e.g. syslogd is running) then there's no timeout involved.
>
>  
>
So am alarm around the call should stop an app from hanging forever 
(i.e. set an alarm of 10 sec, call syslog and if it hasn't returned 
after 10 secs, the alarm will kill that exec)? Is there any way I can 
emulate this condition? I tried sending a STOP signal to syslog-ng - it 
stopped outputting to the syslog file all right - but didn't cause any 
apps to hang - so it's not quite what I'm after...

[I have an app I wrote that writes to syslog that I'm now concerned for 
it's reliability now that I've experienced this]

Thanks! Now that I've installed syslog-ng - I'm *not* expecting to come 
into work to see the same condition tomorrow ;-)

-- 
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1