Bug 132816 (IT_37323)

Summary: glibc in RHEL 3 needs to have syslog.c updated to cvs version 1.42
Product: Red Hat Enterprise Linux 3 Reporter: Neil Horman <nhorman>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: redhat-bugzilla, tao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-20 13:14:11 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Neil Horman 2004-09-17 08:52:26 EDT
Description of problem:
If a root owned process calls syslog while the syslogd daemon is
stopped, it will set the LogType global variable permanently to
SOCK_STREAM, relegating any further syslog messages from that
application to the console, rather than the syslog

Version-Release number of selected component (if applicable):
all pre-RHEL4-Beta 1 versions

How reproducible:

Steps to Reproduce:
1.log in as/su to root 
2.start an application that periodically writes to the syslog
3.stop the syslog daemon
4.wait a sufficient period of time for the app in (2) to attempt to
write a syslog message
5.start the syslog daemon

Actual results:
Messages from the application are not logged in /var/log/messages
until the app is restarted

Expected results:
Messages from the appication should start to appaear in
/var/log/messages when syslogd is restarted.

Additional info:
This is fixed in the sources.redhat.com glibc cvs tree in version 1.42
of misc/syslog.c
Comment 1 Jakub Jelinek 2004-10-06 14:30:12 EDT
The patch is in glibc-2.3.2-95.28 which ought to appear in U4 beta.
Comment 3 John Flanagan 2004-12-20 13:14:11 EST
An errata has been issued which should help the problem 
described in this bug report. This report is therefore being 
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, 
please follow the link below. You may reopen this bug report 
if the solution does not work for you.