Bug 4142 - autofs won't mount with path lengths longer that one
Summary: autofs won't mount with path lengths longer that one
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: autofs
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-07-21 17:53 UTC by abm64239
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 1999-09-01 20:17:56 UTC


Attachments (Terms of Use)

Description abm64239 1999-07-21 17:53:52 UTC
autofs will not mount directories that have more than one
componet in the path.  i.e.

/home    works fine
/home/apps  will not work.

this will not work on a map on the nis server or with a
local map.  I reconfigured the same exact map so the mount
point was a single directory and it worked.  Went back and
changed it to a multiple path and it would not work.  The
error given was the directory did not exist.  Autofs under
other unix systems will mount multiple path entries with no
problems.  Thanks for any help.  We need this to work for
integration into our corporate environment.  Thanks again.

Aaron Miller

Comment 1 Jay Turner 1999-07-22 18:15:59 UTC
Not exactly following you on this one.  Are you saying that you are
trying to mount stuff onto the /home and /homeapps moutn point, or
that you are trying to mount /home and /home/apps on another mount
point.

Comment 2 Bill Nottingham 1999-08-21 19:28:59 UTC
OK, double checking; you have an automounter running on /mnt,
and you want to mount entries on /mnt/foo/bar, correct?

Apologies for the slow response.

Comment 3 Bill Nottingham 1999-08-31 16:06:59 UTC
Do the directories actually exist on the machines?
Autofs will not create the directories to satisfy a
multi-level mount - it won't mount on /foo/bar if /foo isn't
there...


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