[lkml]   [2000]   [Oct]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: syslog() blocks on glibc 2.1.3 with kernel 2.2.x
On 23 Oct 2000, Patrick J. LoPresti wrote:
>Once the name resolution times out, you might expect things to become
>unstuck. But they don't.

Negative. Things have been queued. The deadlock will only go away if the
very next message processed is the named local message. And then it would
have to process a few more local messages so it wouldn't stall again so soon.

>> Per chance are you running the name service caching daemon (nscd)?

Please do. That will reduce the ammount of traffic to the name server.

>> 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.
>I see no documentation for such an option in the syslog.conf man page.
>This is with the current Red Hat 6.2 syslogd (package

It's in the syslogd and syslog.conf man page (sysklogd-1.3.31-16):
Regular File
Typically messages are logged to real files. The file has
to be specified with full pathname, beginning with a slash

You may prefix each entry with the minus ``-'' sign to
omit syncing the file after every logging. Note that you
might lose information if the system crashes right behind
a write attempt. Nevertheless this might give you back
some performance, especially if you run programs that use
logging in a very verbose manner.


PS: as a side note, you can/will lose information even if sync is enabled.
(fsync() will not flush metadata so the file is truncated on restart.)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:41    [W:0.044 / U:26.804 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site