Note that, if you manually create the mount point using mkdir, it will mount.īut, upon restart, OS X removes the mount point, and automounting will fail. $ sudo automount -cvĪutomount: /Volumes/my_mount: mountpoint unavailable This will not work (anymore!) though it "should". Otherwise the automounter will not be able to read the config and fail with a. Make sure you: sudo chmod 644 /etc/auto_nfs etc/auto_nfs (this is all one line): /Volumes/my_mount -fstype=nfs,noowners,nolockd,noresvport,hard,bg,intr,rw,tcp,nfc nfs://192.168.1.1:/exports/my_share net -hosts -nobrowse,hidefromfinder,nosuid Somewhere along the line, Apple decided allowing mounts directly into /Volumes should not be possible: I'll try and download wireshark and see if I can get anything from it, I've heard a few people figure out something about it, but I haven't yet seen any solid solutions.I have spent quite a bit of time figuring out automounts of NFS shares in OS X. Where does this problem lie? Is anyone working to fix it?
I've got other Macs in other offices connecting to other NFS volumes without trouble. I see a lot of posts about this, but no clear answer. Same deal, "lockd not responding" There is just the one Mac in this office, so I've got it using local locks until I can find a proper solution. Mac Pro, 10.5.5 NFS mounted home directory, connecting to some NetApp box, that I don't have admin control of. This computer was just installed this week. There are other Leopard Macs in the same office, connecting to the same NFS volume, and they don't have this problem. As a temporary work around, this user is using a local account until we can resolve this. system.log shows "lockd not responding" I've got NFS using reserved ports, but it's not helping. The user logs in, but nothing works right. IMac 10.5.6, NFS mounted home directory, connecting to a CentOS 5 box that is under my jurisdiction. I've got two separate computers using two separate NFS shares, exhibiting the same problem.
0 kommentar(er)
