Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x

this been addressed (and I missed it) or did the question get diverted? If it has been addressed, just please mail me personally to save traffic on the list. Thanks! -- Stephen Harris [EMAIL PROTECTED] http://www.spuddy.org/ The truth

Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x

. syslog is not a reliable mechanism and many programs have been written assuming they can fire off syslog() calls without worry. Stephen Harris [EMAIL PROTECTED] http://www.spuddy.org/ The truth is the truth, and opinion just opinion. But what

Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x

in. Has this been addressed (and I missed it) or did the question get diverted? If it has been addressed, just please mail me personally to save traffic on the list. Thanks! -- Stephen Harris [EMAIL PROTECTED] http://www.spuddy.org/

Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x

OCK regardless of whether it's local or remote. syslog is not a reliable mechanism and many programs have been written assuming they can fire off syslog() calls without worry. Stephen Harris [EMAIL PROTECTED] http://www.spuddy.org/ The

Re: syslog() blocks on glibc 2.1.3 with kernel 2.2.x

oded assuming that they will not be frozen in syslog(). Linux should not be different in this respect. Hmm... it might be nice to be this a system tunable parameter but I'm not sure the best way of doing that (glibc maybe?) Stephen Harris [EMAIL PROT