Bug 3672 - Performance bugs in syslogd and klogd
Summary: Performance bugs in syslogd and klogd
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sysklogd
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-06-23 15:03 UTC by mch
Modified: 2014-03-17 02:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-09-05 16:58:15 UTC

Attachments (Terms of Use)

Description mch 1999-06-23 15:03:21 UTC

Both syslogd and klogd take much cpu (>10%) without much
output to the log files.

Is there a newer version of sysklogd, or do you know
of any fixes to /etc/syslog.conf that fixes this problem
(i'm using /etc/syslog.conf from RH6.0/x86).


Comment 1 Jay Turner 1999-06-23 15:14:59 UTC
Unable to find this on any of our servers, but am forwarded it to a
developer for further review.

Comment 2 Bill Nottingham 1999-07-26 19:54:59 UTC
Does turning off syncing the file help at all?

Comment 3 mch 1999-07-27 07:52:59 UTC
Haven't tried that. The weird thing is that there isn't much logging
activity going on (less than 100 entries per day in messages and
hardly any entries at all in the other log files). The problem only
shows up when the machine is heavily loaded (load avg well over 1 for
long periods of time).

This problem has been discussed on the linux kernel mailing list, and
I was just wondering if you guys had a fix for it.



Comment 4 mch 1999-08-02 10:06:59 UTC
I've tested turning off syncing now, and it does not help.


Comment 5 Jeff Johnson 1999-09-05 16:58:59 UTC
I see no way to address this request without some idea of what
the cause of the cpu usage is. AFAICT, it's quite possible for
syslogd to receive messages, possibly multiple times a second,
that, because of the configuration in /etc/syslog.conf, are simply
discarded. Please reopen this bug if you have specific suggestions
to reduce cpu usage.

Note You need to log in before you can comment on or make changes to this bug.