Not a problem, just an observation if you use /Volumes/share as a mount point.
I set up the automount NFS as mentioned in the initial report, and discovered
that if you point the mount point to /Volumes then it will conflict with the
other automount services that are running on the machine. I guess after I
have thought about this a bit it makes sense. A quick look at the processes
show that there are three automounts running after setting the exports up
this way.
386 ?? Ss 0:10.14 /usr/sbin/automount -f -m /Network -nsl
391 ?? Ss 0:00.01 /usr/sbin/automount -f -m /automount/Servers -fstab
405 ?? Ss 0:10.37 /usr/sbin/automount -f -m /Volumes /etc/auto.fuel
Users here like to use /Volumes/sharename in their path so I had no option but
to mount NFS drives to /Volumes. The drives mount fine on startup and behave
as expected, but should try to connect to /Volumes/<hostname> then the link
will be broken.
/Volumes normally has a link to the root drive in Volumes too, as well as
other mounted drives.
-rw-rw-rw- 1 howard admin 6148 Jan 24 08:32 .DS_Store
drwxrwxrwx 27 howard 105 874 Jun 27 16:40 indian
lrwxr-xr-x 1 root admin 1 Jun 28 13:14 mullet -> /
These don't show up when the NFS automount runs. The whole /Volumes folder is
read-only.
If you set up NFS mounts through netinfo this doesn't happen, perhaps because
the mounts are handled by the same automount process?
For the rendernodes the separate automount works fine, but for workstations I
have found setting them up though netinfo more robust as they still maintain
the other links in /Volumes.
--
Dylan Penhale
Systems Administrator
Fuel International
65 King Street
Newtown
Sydney
NSW 2042
Phone: xxxxxxxxxx
Mobile: xxxxxxxxxx
Web: www.fuel-depot.com
|