The automount process will not detect changes made to auto_master or other map files unless you tell it. The /etc/fstab file is deprecated in OS X and not recommended. The last two lines in auto_master handle NFS mounts defined in the /etc/fstab file, the common file system mount table in Linux and other Unix flavors. Once again, we see the plus sign telling OS X to look for an auto_home record in the directory service. Here is the default /etc/auto_home file: # Network users who login to the local machine will have their home directories mounted in /home according to the details in /etc/auto_home. The mount point in the local directory is defined, but the remote mounts are defined in the /etc/auto_home map file. Notice the /home entry is set to auto_home, and because it is not a full path, it is assumed to be /etc/auto_home. The plus (+) sign in front of the auto_master entry tells OS X to look in the directory service (Open Directory, LDAP, etc.) for an automount record and use it if found. Here is what the default file looks like on my Mac: # The auto_master defines all “maps” which are collections of automounts related by mount point and organized in one file (or directory service entry). If you are going to mount NFS volumes from a Linux server, there is one gotcha that I covered in an earlier blog post. The /etc/auto_master file controls the auto-mounted Network File System (NFS) file systems. I was not and had to do quite a bit of digging. Many of the advanced features are not documented very well, and this can be an issue unless you are familiar with Solaris. Mac OS X uses an autofs code stack based on Sun’s Solaris version of Unix. It can also dynamically mount network shares on access. Autofs is often used in enterprise environments to set up network-based home directories and other network mounts for users at login.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |