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

From: Ricky Beam (jfbeam@bluetopia.net)
Date: Thu Oct 26 2000 - 10:46:42 EST


On Thu, 26 Oct 2000, Igmar Palsenberg wrote:
>> Per chance are you running the name service caching daemon (nscd)? I'd
>> also guess you aren't disabling fsync() for your sysylog files (it's part
>> of the syslog.conf format) -- this is a conciderable drain on syslogd.
>
>Agree. It is there for a reason : I case the system hangs, you at least
>get the last messages. But it is indeed a major drain. I've send Patrick a
>small path that makes reverse lookups a config option.

Sadly, you WILL still lose entries if the system crashes before fs metadata
has been flushed to disk. Unless the inode has the correct size stored, the
crap fsync()ed to disk doesn't make much difference.

(This is amplified by dcache.)

--Ricky

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue Oct 31 2000 - 21:00:18 EST