Bug 8630
Summary: | syslog doesn't log ssh after upgrade | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | jrs |
Component: | sysklogd | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | CC: | jrs, rvokal |
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: | 2000-02-01 19:37:32 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
jrs
2000-01-19 19:25:47 UTC
When you say that you compiled ssh from source, it is *not* a version compiled against libc5, correct? *** This bug has been marked as a duplicate of 7214 *** Yes, ssh-1.2.27 is compiled against libc6. I'm not so sure that this is really a duplicate of 7214. My sendmail (which came from the RH6.0 rpm) continued logging. When I repeated the experiment on an identically configured AMD K6-3 box, I found that after upgrading sysklogd, I was able to get sshd to resume logging simply by kicking it: kill -s SIGHUP <pid of currently running sshd> |