From: Gary Jaeger <gary@(email surpressed)>
Subject: -1 added to mounted AFP volumes OS X
   Date: Tue, 31 May 2011 13:14:11 -0400

not strictly a rush question but I 'm hoping somebody here has the answer. 

Why does OS X sometimes add a -1 to a mounted volume name? It hits us when using rush and boxes on the farm naturally can't resolve

/server/foo/bar-1/submit-maya.pl

when the correct path should be:

/server/foo/bar-1/submit-maya.pl

artists can't see it in the finder. i.e the share appears to the correct name. But if you look at it in terminal it shows up with the -1 attached. Indeed if we inspect /Volumes we see the duplicate names. 

/Volumes/bar
/Volumes/bar-1


. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com	

On 05/31/11 10:14, Gary Jaeger wrote:
> /Volumes/bar
> /Volumes/bar-1

	Yes, I've seen that behavior since I first started messing
	with OSX back in version 10.1, and it persists. Very annoying!
	It's one of the many reasons I don't trust apple's automated
	behaviors for mounting drives.

	I googled for 'osx duplicate mounts' and found a few things:
	http://support.apple.com/kb/TS2474
	http://superuser.com/questions/20879/how-to-remove-duplicate-ghost-network-drive-on-os-x
	https://discussions.apple.com/message/6958171?messageID=6958171

	It's probably either the Finder or Automounter or both working
	together to be the cause, but I never actually tracked this down.

	If you find its manual interaction in the Finder causes this,
	like say the user invoking 'Connect to' even though the drive
	is already mounted, there's a 'defaults' command that lets you
	disable the Finder's 'Connect to' feature. (This assumes you have
	some other approach in place that mounts the server for you, eg.
	a boot script that mounts the drives on startup)

	There's a whole list of 'defaults' commands here:
	http://secrets.blacktree.com/?show=all
	(Note the 'More' link at the bottom of that page)

	The one I'm talking about would be "prohibit use of Connect To", ie:

defaults write com.apple.finder ProhibitConnectTo -boolean [YES|NO]

	I haven't tested this myself, but it might be worth some
	experimenting.

	If you don't like the automounter, you can disable it
	via the /etc/hostconfig: AUTOMOUNT=no. This disables the
	automounter from starting on boot. (Not sure if the automounter
	is the cause though)

	You can configure mounts with a boot script using e.g. this technique:
	http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1847+1847

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

Thanks Greg. I'm going to try this. I'm sure I'll break something :)

On May 31, 2011, at 10:53 AM, Greg Ercolano wrote:

> 	You can configure mounts with a boot script using e.g. this technique:
> 	http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1847+1847

. . . . . . . . . . . .
Gary Jaeger // Core Studio
86 Graham Street, Suite 120
San Francisco, CA 94129
(Tel# suppressed)
http://corestudio.com	

On 05/31/11 13:15, Gary Jaeger wrote:
>> You can configure mounts with a boot script using e.g. this technique:
>> http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1847+1847
> 
> Thanks Greg. I'm going to try this. I'm sure I'll break something :)

    Feel free to contact me directly if you have specific problems,
    and I can follow up to that thread with details.

PS. One thing you might want to do in the mount flags is include
    sec=sys to ensure kerberos isn't used, eg:

Mount 192.168.1.14:/net  /meade/net  "intr,bg,sec=sys"
                                              ^^^^^^^

    I know some folks have seen kerberos errors on Mac NFS servers
    when they didn't think they had kerberos enabled. According to
    'man mount_nfs', the docs for sec= says:

        "When this option [sec=] is not given the security mechanism
         will be negotiated transparently with the remote server."

    ..which I take to mean 'anything can happen', so it's probably best
    to disable kerberos in the mount flag by setting it to 'sys'. See also:

    "Mac OS X Server version 10.5: About Kerberized NFS"
    http://support.apple.com/kb/TA24986?viewlocale=en_US


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