Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 155652 - automounter tries mounts that doesn't exist
Summary: automounter tries mounts that doesn't exist
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: autofs
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Jeff Moyer
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-22 09:06 UTC by David Juran
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-04-22 11:38:15 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description David Juran 2005-04-22 09:06:56 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.4) Gecko/20050318 Red Hat/1.4.4-1.3.5

Description of problem:
We have our home directories mounted using a NIS map under /users.

schiphol 37: ypcat -k auto.master
/-  -rw
/users auto.users       -rw
/nfs/ipatinga/isosrv auto.isosrv        -ro
/nfs/vm auto.vm         -rw

schiphol 38: ypcat -k auto.users|head
chrisjoh -proto=tcp
elmroth -proto=tcp

Now if I try 

schiphol 39: cd /users/foo
/users/foo: No such file or directory.

But in /var/log/messages I get a log entry:
Apr 22 10:53:38 schiphol automount[1461]: failed to mount /users/foo

And of course there is no foo in auto.users.
This is of course not a problem in itself, it just looks a bit weird...
RHEL3 has the same behaviour.

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

How reproducible:

Steps to Reproduce:
1. cd /users/foo

Additional info:

Comment 1 Jeff Moyer 2005-04-22 11:38:15 UTC
This message does not mean that automount tried to mount the entry.  It can mean
that it failed to find an entry for foo in the map.

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