Bug 57914 - spurious automount messages in system log
Summary: spurious automount messages in system log
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pam
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-01 13:34 UTC by rdt
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-01-01 15:33:22 UTC
Embargoed:


Attachments (Terms of Use)
/var/log/messages (1.91 KB, text/plain)
2002-01-01 13:36 UTC, rdt
no flags Details

Description rdt 2002-01-01 13:34:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.7-10 i586)

Description of problem:
Every interactive login/out generates spurious automount messages.




Version-Release number of selected component (if applicable): 
pam-0.75-19


How reproducible:
Always

Steps to Reproduce:
1. login or logout at the gdm screen
2.
3.
	

Additional info:

Comment 1 rdt 2002-01-01 13:36:32 UTC
Created attachment 41572 [details]
/var/log/messages

Comment 2 rdt 2002-01-01 15:33:16 UTC
The messages don't appear if I use /misc instead of /mnt as my
automount directory.  This is an easy workaround, but the messages
shouldn't appear regardless.

Comment 3 Nalin Dahyabhai 2002-03-08 00:19:20 UTC
The mount attempts are being triggered because pam_console is attempting to give
the user permission to access those directories.  This is used to make
hotplugging work.  If you don't want those directories touched, you'll need to
remove references to those directories from /etc/security/console.perms.

For what it's worth, it hits me on my workstation at work as well (I also modify
the automounter configuration from its default, which doesn't cause this to
happen), but it works the way it's supposed to, so I'm closing this as won't fix.


Note You need to log in before you can comment on or make changes to this bug.