Bug 155652 - automounter tries mounts that doesn't exist
automounter tries mounts that doesn't exist
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: autofs (Show other bugs)
All Linux
medium Severity low
: ---
: ---
Assigned To: Jeff Moyer
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2005-04-22 05:06 EDT by David Juran
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-22 07:38:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Juran 2005-04-22 05:06:56 EDT
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
/- auto.direct  -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     fillmore.carmen.se:/vol/vol1/users4/&
elmroth -proto=tcp      fillmore.carmen.se:/vol/vol1/users5/&

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 07:38:15 EDT
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.