![]() Not only does Automounter do all I want it does it more elegantly and efficiently than the others. I then tried Automounter (sure wish they had a trial version but there is always a refund option from the MAS). Mountain was doing OK but it's developer is likewise incommunicado. Not only is there no mention of the incompatibility (Macupdate or website) the developer was totally unresponsive. I bought Remount and was ignorantly blissful until I tried it on my HighSierra machine. I first tried some others, Remount and Mountain. Thus began a search for 3rd party solutions which ended with my being perfectly content with Automounter and impressed by developer support. Once unmounted I had the choice of either logging out/in or manually mounting the drives - both a pain in the you know what. My ISP changed and connectivity, while pretty dang good, has issues. The wildcard information is in the Wildcards section, while information about using ampersands is available in the Substituting the map key entry section.For years I was happy with having networked drives (USB drives attached to AirportExtreme) mount as Login Items. For example, the following entry could be added to /etc/auto_home to have appropriate shares mount as /home/username_goes_here:įor more information on properly formatting entries for /etc/auto_home, including information on using wildcards ( * ) and ampersands ( &), I recommend reading the man page for /etc/automaster. If you want to have an NFS mount show up under /home for each user that logs in, you can also use wildcards ( * ) and ampersands ( &) in /etc/auto_home. If the network home is mountable from the server from a home NFS share, the following entry could be added to /etc/auto_home to have the designated share mount as /home/username: If NFS is an available option, this may be better because no usernames or passwords will need to be stored in /etc/auto_home in order to mount an NFS share. If this is a multi-user system, subsequent users will have no access to /home/username on that Mac. ![]() The first person to access /home/username will have full access to the share as that user on the server. ![]() autofs on OS X doesn’t support using Kerberos authentication, so there’s no good way to secure the connection.Ģ. The username and password will need to be stored in /etc/auto_home as part of the mount entry. That said, having an SMB mount entry in /etc/auto_home may not a good idea for the following reasons:ġ. You will also receive a “ No locks available” or similar “Host is down” error if the password is wrong or missing. : & ? ^ _ ~”), you may receive a “ No locks available” error message and the share will not mount under /home. To do what my user wanted to do, the following entry could be added to /etc/auto_home to have the designated share mount as If you have a password longer than 8 characters, or if the password has special characters in it (like “! # $ % & ‘ ( ) * +, –. It’s listed in /etc/auto_master as a mountpointĪfter talking with Apple’s enterprise support folks and doing some additional research, the file that controls what’s mounted in /home is the /etc/auto_home auto mount file. Nothing appears to be stored in it by defaultĢ. He wanted to be able to mount smb://servername/home$/username to /home/username on his Mac, so that it matched the mountpoint of his network home on his Fedora box.Īt the time, here’s what I knew about /home:ġ. His network home directory was available via SMB on his Mac as smb://servername/home$/username. In this case, the person in question works on both Fedora Linux, where his network home directory was mounted as /home/username, and on OS X. One of my users at work asked me recently about symlinking his network home folder to /home on his Mac running 10.9.2 and wanted to check to see if it was safe to do so.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |