recentpopularlog in

kme : automount   15

pam_mount - ArchWiki |
This avoids double mount attempts and errors relating to dropped privileges.
pam  pam_mount  network  filesystem  automount  cifs  maybesolution 
april 2018 by kme
mount - Windows 8 ISO Mounting at startup / permanently - Super User
Basically you want an ISO file to be mounted each time you Logon to your PC. You have two methods to do this:

Open run and type in shell:startup, this will open up the Startup Folder. Place a shortcut to ISO here, and This will work.

(Better Option) Execute this in Admin CMD

reg add HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run /v "Mount ISO" /d "{location to ISO}"
win8  iso  windows  automount  virtualdisk  solution 
may 2014 by kme
Gregor Jasny - Google+ - How to set up permanent NFS mounts with #mountainlion …
How to set up permanent NFS mounts with #mountainlion

Starting with Disk Utility 13 from Mountain Lion, the menu option to manage NFS mounts is gone. One has to use the following commands to create a permanent NFS mount:

# create
sudo dscl . -create /Mounts/foo
sudo dscl . -create /Mounts/foo VFSLinkDir /Volumes/share
sudo dscl . -create /Mounts/foo VFSOpts resvport ro nosuid
sudo dscl . -create /Mounts/foo VFSType nfs
sudo dscl . -create /Mounts/foo RecordName

# verify
sudo dscl . -list /Mounts
sudo dscl . -read /Mounts/

I learned that there is a graphical tool called "Directory Editor". It can be launched via

open /System/Library/CoreServices/Directory\

So this solves the mystery of where the 'static' autofs mounts were coming from--directory services. Just fire up the (now cleverly hidden) Directory Utility and click on the "Directory Editor" toolbar button, then choose Viewing -> "Mounts" in node -> "/Local/Default."
mac  osx  solution  nfs  autofs  automount  diskutility  mystery 
january 2014 by kme
Mounting NFS volumes in OS X - TechRepublic
5. Expand the Advanced Mount Parameters section. Here you can pass some extra parameters to the NFS mount. The ideal value to place here is: resvport,nolocks,locallocks,intr,soft,wsize=32768,rsize=3276 (Look at the mount_nfs manpage for all of the available options and what they mean).

So, yes, they are give as options to '-o option1,option2', although ns_fstab.c ( may be doing some trickery where it recognizes other flags as well (e.g., '-P').
solution  autofs  automount  mac  osx  networking  sysadmin  queestion 
january 2014 by kme
Introduction to Autofs in Mac OS X | Low End Mac
And I thought I was supposed to be seeing something in /home for *local* users--like a compatibility 'shim' for where the usual Unix home folders are stored--but nope. It's for network users who have logged in with an account that was authenticated via directory services.
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. It is an example of an indirect map. The mount point in the local directory is defined, but the remote mounts are defined in the /etc/auto_home map 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.

Here is the default /etc/auto_home file:

# Automounter map for /home
+auto_home # Use directory service
autofs  mac  osx  nfs  automount  reference  tutorial  networking  sysadmin  question  solution 
january 2014 by kme
autofsd: /usr/sbin/automount terminated...: Apple Support Communities
Beautiful, thanks for the source info.

Looks like the automount arg processing is weak. An option arg append length check was failing.

Forgoing the automounter was the simplest option.

Sticking all the mounts in a script to be run as needed solved the problem:


sudo mount -o $NFS_OPTS server:/path /local/path


as needed.

In my case it was using Disk Utility to create a static NFS mount, while trying to pass it '-o browse' (as opposed to its default, which looks like
"map -static on /Volumes/sulaco_share (autofs, automounted, nobrowse)"). The resulting error message when invoking 'sudo automount -vc' was:
Assertion failed: (strlcat((mntops_out), (","), (optlen)) < (optlen)), function process_fstab_mntopts, file /SourceCache/autofs/autofs-207.1/automountlib/ns_fstab.c, line 171.

NB: The 'static' automounts created by Disk Utility (in 10.7 maybe down to 10.5) are created through directory services. That's why you don't see anything in /etc/fstab. See for the detailed info that led to this epiphany.
mac  osx  sysadmin  nfs  automount  autofs  diskutility  errrormessage  solution 
january 2014 by kme
Automount NFS in OS X | Your Mac / Linux Guy
The only way I’ve found this to work – with limitations; see below – is to instead append `browse` to the `AUTOMOUNTD_MNTOPTS=…` line in `/etc/autofs.conf`; e.g.

This causes automounted mounts to behave as follows – WHILE ACTUALLY MOUNTED:

* They show up *individually* on the Desktop – assuming the Finder option to show connected servers on the Desktop is turned on.
* in the Finder sidebar, only the *server* – not the individual mounts – shows up in category Shared as connected – implied by the eject icon next to it – assuming you have the Finder option to show connected servers in the sidebar turned on.
* Also note that if you eject the server via the Finder sidebar, the icons disappear from the Desktop – yet, the shares will continue to be accessible, by virtue of being automounts that reconnect on demand.

Another useful tidbit, although unrelated to the problem I was having:
One last thing to mention. You will probably wish to disable the creation of .DS_Store files on network volumes when using automounts. The Finder has a bad habit of leaving these files open, so your automounted shares will not unmount after set idle times like they’re supposed to. To keep your Mac from writing .DS_Store files to network drives, run the following defaults command in the terminal. This is a per-user setting.

defaults write DSDontWriteNetworkStores true
automount  autofs  nfs  mac  osx  finder  maybesolution  DS_Store  annoyance  networking 
january 2014 by kme
10.6: Add NFS Mounts using Disk Utility - Mac OS X Hints
This is getting me soooo close. Turns out the 'nobrowse' command is passed to these automounts by default, so they don't show up in Finder, but I want that. Evidence suggests that '-o browse' might work ordinarily, but when I restart automountd (see I get this error:
Assertion failed: (strlcat((mntops_out), (","), (optlen)) < (optlen)), function process_fstab_mntopts, file /SourceCache/autofs/autofs-207.1/automountlib/ns_fstab.c, line 171.

Solution at - yes, those "Advanced Mount Parameters" are passed as comma-separated options to '-o'. Unsure whether '-o browse,nobrowse' will cancel and blow up the computer or not.

NB: This capability was removed from Disk Utility in Mountain Lion (10.8). There's a third party (non-free) utility called NFSManager ( which can fill the gap, or you can manually create these mount points using Directory Services utilities (see
nfs  mac  osx  lion  automount  autofs  diskutility  maybesolution  errormessage 
january 2014 by kme
services - How to reload autofs on Lion without restarting? - Ask Different
this works for me:

sudo automount -vc

Problem being, the 'service' command was removed in Lion or something, so:
sudo service stop
sudo service start

doesn't work anymore, but this does:
You can use launchctl instead of service:

sudo launchctl stop
autofs  automount  nfs  mac  osx  service  solution 
january 2014 by kme

Copy this bookmark:

to read