Bug 3896

Summary: pam-console logout isn't triggered from xdm
Product: [Retired] Red Hat Linux Reporter: Steve Holland <sh1>
Component: XFree86Assignee: David Lawrence <dkl>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.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: 1999-07-15 21:26:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Steve Holland 1999-07-04 21:08:37 UTC 
If one switches the default console to xdm from gdm
under redhat 6.0, the pam-console logout actions are
not triggered properly and the ownership of /dev/dsp,
/dev/cdrom, etc. get stuck with the first user to
log in after a reboot.

When that user logs out the following message is generated
in /var/log/secure:
Jul  4 12:57:28 myhost pam_console[786]: Could not open lock
file /var/lock/console/sdh4, disallowing console access

then on the next attempted login:
Jul  4 12:57:58 myhost pam_console[872]: console file lock
already in place /var/lock/console.lock
Comment 1 Preston Brown 1999-07-15 21:26:59 UTC 
*** This bug has been marked as a duplicate of 3743 ***
Comment 2 openshift-github-bot 2017-04-25 17:26:38 UTC 
Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/ad17d03de5104e4b4f99c13b9cc696078927672a
Pick from issue3896