Am I to assume that because I have not gotten any replies, that no one else is having this problem? Or that no one else has noticed they may have this problem because it has not impacted them in any way? Try doing the following and see what you get on your systems. who -a Do you see multiple entries for the same pts? utmpdump /var/run/utmp Will show more detail information about each entry. Jack Allen -----Original Message----- From: redhat-list-bounces@xxxxxxxxxx [mailto:Jack.Allen@xxxxxxxxxxxx] Sent: Tuesday, September 05, 2006 6:32 PM To: redhat-list@xxxxxxxxxx Subject: utmp problems Has anyone else seen utmp corruption running AS 4.0 with all the latest up2dates? That is there are multiple entries for the same ID (pts/*). When there are duplicates, most have a status of DEAD, but per the documentation, there should only be one entry with the appropriate status. Sometimes I have seen where it looks like the user never logged out, but I know for sure another user is using the pts/*. We have an application that uses logname command and it returns the wrong login name then. The application also uses the getlogin() function and it fails the same way. This leads me to believe the logname command uses the getlogin() function also. Through my searching I can find mention of problems when some old version of xterm was run that did not use the same utmp structure. This would seem to cause just plain old corruption, because the structures were not the same size. The problem I am having, acts like a file update issue or locking and or not locking as needed. Thanks: Jack Allen -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
