From: Dylan Penhale <dylan@(email surpressed)>
Subject: Re: [OSX/ADMIN] Tiger -- Initial Report
   Date: Tue, 28 Jun 2005 18:21:05 -0700

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

Dylan Penhale wrote:

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.

	Yes, a few others have corroborated this opinion too.

	What exactly is the 'NetInfo' technique you're using?
	Is this where you hack mount points into "mounts" database in NetInfo?

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)

On Wed, 29 Jun 2005 11:33 am, Greg Ercolano wrote:

> [posted to rush.general]
>
> Dylan Penhale wrote:
> > 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.
>
> 	Yes, a few others have corroborated this opinion too.
>
> 	What exactly is the 'NetInfo' technique you're using?
> 	Is this where you hack mount points into "mounts" database in NetInfo?

Exactly. I started by using NFS Manager which give you all of the options in 
one nice GUI, then ended up just entering the data using Netinfo Manager 
manually. I think if I where to roll out NFS network wide I would do it with 
rsh though:

mounts

{
  "name" = ( "mounts" );
  CHILDREN = (
    {
      "opts" = ( "-P" );
      "name" = ( "hostname:/home" );
      "type" = ( "nfs" );
      "dir" = ( "/hostname" );
    }
  )
}

niload -r /mounts . < mounts_table

etc..

It seems that this way doesn't interfere with the other things in /Volumes

Of course it would be nice to stop using /Volumes but thats another thing. 


-- 
Dylan Penhale
Systems Administrator
Fuel International
65 King Street
Newtown
Sydney
NSW 2042

Phone:  xxxxxxxxxx
Mobile: xxxxxxxxxx
Web:    www.fuel-depot.com