Bug 54561
Summary: | A bad syslogd.conf make computer freeze | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | grenier |
Component: | sysklogd | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | stimits |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-30 21:14:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
grenier
2001-10-12 13:25:04 UTC
I have found that syslogd on RH 7.1 attempts to restart 6 times. The restart mechanism is incorrect, and tries to spawn too many syslogd daemons. I have also found that attempting a shutdown or xinetd restart during that time will cause hard lockup or oops. In my particular case, I'm using SMP. This is the second time I've hit this problem, and it should be moved up in priority. Just clearing out old bugs here. This bug was fixed a long time ago, but never got closed. It is certainly fixed in the current version of syslog: sysklogd-1.41-22. |