this will sow you a list of volumes and what IPs they are exporting to.
1) open NetInfo Mgr.
3) select the mounts directory
4) click on the the "add new directory' icon and type Cmd+n
5) Using the Directory menu add the following properties and values to the ne entry
name ........................ myNfsServer:/mydir/
type .......................... nfs
dir ............................. /the/mount/point/of/the/shared/volume/
6) Cmd + s to save or File>Save
8) Try loggin out to incorporate these changes, but I have always had to Restart
I did the same thing with my red hat box. I configured mac os x to mount the volume on startup, but I haden't configured the redhat box correctly. I needed to add a line to /etc/hosts.allow for my computer.
portmap : 192.168.1.0/255.255.255.0 : allow
I think solaris will be different because it may have a different pam or something.
Also, the only way to make your computer boot up now (asuming that the nfs connection fails on startup), is to boot holding apple-s. That gets you in to single user mode. Then mount your file system just like in the instructions you are given. Next, you have to figure out how to use nidump and niload to remove the netinfo domain you created under mounts. Its quite annoing, so I gave up and fixed my redhat box.
Another thing I just realized, you may be able to simply remove it from startup by removing the files in /System/CoreServices/StartupItems/mounts/
really, all you need to do is remove the 'mounts'. It might be labeled differently, maybe as nfs or something. But if you remove it, then it will no longer be accessed on bootup.
When editing net info use the following:
Property | Value(s)
vfstype | nfs
dir | /mnt
name | nfs.server:/dir/
opts | net, -P, -b, -s
net makes the nfs automounter take over and mounts it in /private/Network/Servers/
-P is NOT ignored as said in the man pages and is needed when connecting to Linux box's and probally other UNIXs too
According to the man page:
-b If an initial attempt to contact the server fails, fork off a
child to keep trying the mount in the background. Useful for
fstab(5), where the filesystem mount is not critical to multius-
This prevents your computer from freezing if there is a problem with the export.
PS I might have changed some other stuff so if this doesn't work let me know
- i don't know if you know this, but there's an excellent article about mounting nis (and nfs) at: www.bresink.de/osx/nis.html#Versions
- at the moment i'm trying this, there's just ONE damn thing that doesn't work for me:
after i have set up the lookupd.txt, saved it and getting ready to put at the end of the string /locations/lookupd using the two commands
niutil -create . /locations/lookupd
niload -r /locations/lookupd . <lookupd.txt
i get a
token "-nil-2 error at line 24 (and in the script there is no nil at line 24)
- what gives?
if this works it should be possible to access a user db from the unix server, complete with directory and all!
hope this either helps or brings some more confusion
first problem solved - apparently had a typo in there somewhere - bu still nothing is happening. I read somewhere that it was neceesary to generate a mount map for os X on the server side, since the nis automount is very different from the os X automounter, but i haven't tried it out yet - any experiences?