Hannes Reinecke writes...
> Rick Richardson wrote:
> >
> > With "amd", we had no trouble automounting our Network Appliance NFS
> > server on Redhat 5.2. Here is our "amd.conf" file:
> >
> > /defaults fs:=${autodir}/${rhost}/root/${rfs};opts:=nosuid,nodev
> > * rhost:=${key};type:=host;rfs:=/
> >
> > But with "autofs" on RH 6.0, we cannot get it to automount the Network
> > Appliance NFS server. Manual NFS mounts of the appliance work.
> > Autofs will automount other Linux boxes and Solaris boxes.
> >
> > Here is /etc/auto.master:
> > /net /etc/auto.net --timeout 60
> >
> > and here is /etc/auto.net:
> > * &:/
> >
> Well, it doesn't work that way (unfortunately).
> Autofs is only capable of resolving one level of depth, the rest is
> assumed to reside on the remote disk.
I don't think thats the problem. Using the configuration above,
"ls /net/machine" mounts all the exported filesystems on "machine",
even with autofs. So if "machine" has "/" and "/home", then both
of those filesystems get mounted under /net/machine (although,
oddly, /net/machine/home won't appear in the mount table.
Autofs just seems to have a problem mounting the Network Appliance
this way. I *think* it is because the Network Appliance doesn't have
an exported "/" filesystem, just /xxx, /yyy, /zzz.
"amd" seems to deal with this just fine, whereas autofs does not.
> So when you'd like something (NA-NFS/NeXTish):
> /Net/<servername>/<share>
>
> then you'd be better off creating separate mount-maps for each server,
> which are then mounted under /net/<servername>
>
> So /etc/auto.master would look like:
> /net/fs1 /etc/auto.net.fs1 --timeout 60
>
> And /etc/auto.net.fs1 would look like:
> * fs1:/&
I got no joy with this configuration, either.
-Rick
--
Rick Richardson [EMAIL PROTECTED] http://RickRichardson.freeservers.com/
"Just run your business as if: 1) you own 100% of it; 2) it is the only asset
in the world that you will ever have; and 3) you can't sell or merge it for
at least a century." - Warren Buffet to Berkshire's CEOs.
