Bug 14808

Summary: old libc application not logging to syslog since 6.1
Product: [Retired] Red Hat Linux Reporter: Gary Marshall <gary>
Component: libcAssignee: Cristian Gafton <gafton>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-07-28 15:35:43 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 Gary Marshall 2000-07-28 15:35:41 UTC
An application (shtml.exe from frontpage 4.0.4.3)
logs syslog messages properly under RH 6.0
but not under 6.1 or 6.2.

All 3 systems report:
    sysklogd-1.3.31-x
    libc-5.3.12-31

The 6.1 system also has:
    compat-glibc-5.2-2.0.7.1

There also seems to be other compatibility
issues with this app. But we remain clueless
without logging.

Comment 1 Bill Nottingham 2000-07-28 18:41:00 UTC
It's using the wrong socket type in libc5. Go to:

http://www.redhat.com/support/errata/rh42-errata-general.html#syslogd,

grab the libc5 binaries there, and put them in /usr/i486-linux-libc5/lib
(or whatever the directory is called; it's something close to that.)


Comment 2 Gary Marshall 2000-07-31 14:17:00 UTC
1) Links at http://www.redhat.com/support/errata/rh42-errata-
general.html#syslogd are old

2) Forcing an install of libc-5.3.12-18.5.i386.rpm has no effect
   (these install in /lib not /usr/i486-linux-libc5/lib; havent
    tried building from sources yet)

3) Installing sysklogd-1.3.31-0.5.i386.rpm gets us logging again
   (guess we will live under the shadow of syslog DOS attacks)