Bug 10363 - Invalid socket causes syslog to spin
Invalid socket causes syslog to spin
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: sysklogd (Show other bugs)
6.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
:
: 17188 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-03-26 17:39 EST by scottyin
Modified: 2014-03-16 22:13 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-03-27 11:54:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description scottyin 2000-03-26 17:39:04 EST
Using the -a option on syslogd to specify a log socket in a directory that
does not exist will cause syslogd to drive CPU usage to 100% and refuse to
listen to log requests on legit sockets.  This means that if you aren't
logged in as root, you will have to hit the reset button, because su,
sshd, etc. all want to write to syslog before they let you become root.

example:

/sbin/syslogd -m 0 -a /tmp/dir_that_doesnt_exist/log

causes CPU usage to go to 100% and local syslog requests to lock up.
Comment 1 Bill Nottingham 2000-03-27 11:54:59 EST
Fixed in sysklogd-1.3.31-17.
Comment 2 Bill Nottingham 2000-10-02 18:16:12 EDT
*** Bug 17188 has been marked as a duplicate of this bug. ***

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