Bug 151078
Summary: | utmp corruption on telnet server | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Steve Hitterdal <sdhitter> |
Component: | util-linux | Assignee: | Karel Zak <kzak> |
Status: | CLOSED CANTFIX | QA Contact: | Ben Levenson <benl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | ||
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: | 2005-09-08 10:42:20 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
Steve Hitterdal
2005-03-14 17:23:25 UTC
Please, update to the latest telnet-server version. In the version >= 1:0.17-26.EL3.1 is bugfix: * Thu Jan 13 2005 Jason Vas Dias <jvdias> - 1:0.17-26.EL3.1 - bug 143929 / 145004 : fix race condition in telnetd on wtmp lock - when cleanup() is entered from main process and in signal - handler I'm not 100% sure, but it's possible that there is a connection between your problem and wtmp lock problem. We have been testing the 2.4.21-31 beta kernel and the telnet server has been running for 7 days without encountering utmp corruption. We will continue to monitor the server but we are hopeful that this can be a resolution to our problem. The 2.4.21.31 beta kernel had utmp corruption after an uptime of 13 days. We have upgraded to the telnet-server-0.17-26.EL3.2 and will report if utmp corruption occurs with the new telnet server. Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received the feedback we requested, we will assume the problem was not reproduceable or has been fixed in a later update for this product. Users who have experienced this problem are encouraged to upgrade to the latest update release, and if this issue is still reproduceable, please contact the Red Hat Global Support Services page on our website for technical support options: https://www.redhat.com/support If you have a telephone based support contract, you may contact Red Hat at 1-888-GO-REDHAT for technical support for the problem you are experiencing. |