path to shared directory on second volume

[lobsangdibbler]

On OS X server 10.2 I have a set of directories I serve up through NFS and automount via netinfo. The catch is that these directories sit on a second disk on my server. So they are in: /Volumes/Disk2/DirName

Fine. I can access them from any of the netinfo clients as:

/Network/Servers/ServerName/Volumes/Disk2/DirName

HOWEVER, I also want the same path to work when I access them from the server! That is, a user logging into the server console (which we do often) should still be able to see the shared directories in the same path. But they can’t because /Network/Servers/ServerName ON THE SERVER points to Disk1 of the server! This seems like a bug in that /Network/Servers/ServerName should always point to /, not to the contents of the first volume on /

Suggestions? I have tried symbolic links, but what I really need is someway for /Volumes to be “visible” to the finder on the server… Because of course
/Network/Servers/ServerName/ does have Volumes as a subdirectory, but it isn’t “seen”

Thank!

-m

[Cabbage]

[code:1:a1de4b51da] need is /Volumes to be "visible" to the finder [/code:1:a1de4b51da]

Open this file in a text editor
[b:a1de4b51da]/.hidden[/b:a1de4b51da]

Notice the dot before the h.

For me this file looks like this
[code:1:a1de4b51da]automount
bin
cores
Desktop DB
Desktop DF
Desktop Folder
dev
etc
lost+found
mach
mach_kernel
mach.sym
opt
private
sbin
tmp
Trash
usr
var
VM Storage
Volumes
[/code:1:a1de4b51da]

Delete the last line. Save the file. Quit/Relaunch the Finder. Open a new Finder window on / and Volumes should be there.

[lobsangdibbler]

Well it worked – sort of. That is, I can now see /Volumes from the finder. But… I have a volume that holds my mp3s and it is references as /Network/Servers/MachineName/Volumes/VolName/FolderName

This works on all machines on the network, EXCEPT the machine that serves up the volume. On that machine if you click through /Network/Servers/MachineName/Volumes/VolName/FolderName you get to the right place and iTunes will select it, but it doesn’t “see” it.

Ideas?

-m

[Cabbage]

Try making a symbolic link that points to
/private/Network/Servers/<whateveryourpathshouldbe>

[lobsangdibbler]

No. The problem is that the folders ACTUALLY exist in this location on the SERVER. Everything is fine when one logs onto any machine OTHER than the server. But, if I log on to THE SERVER, none of the references are correct. I am not sure what the finder is using for a reference, but whatever it is, it doesn’t work on the actual machine that is serving up (thru NFS) the volumes.

-m

[tim914]

The /Network/Servers/Volumes (and it’s real identity of /private/Network/Servers) is only used for mounting remote volumes. In fact, if you try to mount your local volume as a network volume, you’ll most probably be visited by the 3000 error faerie 😈 .

There really isn’t a way under the current environment to make a local volume look like a remote volume without using a symlink as previously mentioned.

Tim

[lobsangdibbler]

But Tim…

The server is of course part of the same netinfo domain, so it automounts the same (its own) volumes and puts them in Network/Servers/

The funny thing is that this part is fine – it is the confusion about how it SHAREs them that is odd – since they are on a second volume, on the clients it puts them in /Network/Servers/SvrName/Volumes/VolName/DirName

On its little own self it just puts them in /Network/Servers/SvrName/DirName

???

Thanks much, Mike

[tim914]

Sorry – wasn’t too clear there. It’s the motion of trying to get the system to mount itself under /Volumes that gives the 3000 error. Otherwise root (/) on the server will always be root under the /Network/Servers/ hiearchy. In fact, if you issue an “ls -ld /Network/Servers/YourServer”, you’ll discover that it’s a symlink to “/”.

Therefore, /Volumes on the server will equate to /Network/Servers/ServerName/Volumes. In my case, our RAID farm shows up there. This is where you’d need to create a symlink:

[code:1:a504e44b5b]ln -s / /Volumes/MyMachineName[/code:1:a504e44b5b]
Effectively creating a hook between the two worlds that should imitate your remote system paths on the server.

Tim

[Author]

Posts