More on Leopard’s automounter
I had the Leopard automounter more or less working happily but there was one setback. A combination of Finder’s and Office’s braindead behaviour was triggering many many automount lookups which showed in the LDAP logs:
filter="(&(|(objectClass=automount))(|(automountKey=.DS_Store)))" filter="(&(|(objectClass=automount))(|(automountKey=.hidden)))" filter="(&(|(objectClass=automount))(|(automountKey=\2A)))" filter="(&(|(objectClass=automount))(|(automountKey=\2A)))"
This was because the Mac wanted to see what was under /home
, on which home directories were automounted. It would be annoying if all it did was fill my LDAP logs with this spam. When the automounter causes Rebecca’s machine to kernel panic once every few days, it gets extremely tiresome.
My response to this was to change the automount rules so that /home
was managed by auto_static instead of auto_home.
dn: automountKey=/home,automountMapName=auto_static,ou=mounts,dc=iain,dc=cx objectClass: top objectClass: automount automountKey: /home automountInformation: -fstype=nfs,tcp,rw,intr files:/home
On the Linux clients this worked. The Macs, however, were having none of it. With this setup /home
was completely inaccessible. All attempts to look at the directory, even ls -ld failed with Permission Denied. The solution is to comment out the /home line in /etc/auto_master
.
As a poster in the above thread puts it, sigh.
Can’t you simply remove the “-nobrowse” from the “auto_home” entry in “/etc/auto_master”?
Comment by Tron — 2008-01-21 @ 21:58:08
Nope. That doesn’t work.
Comment by iain — 2008-01-23 @ 00:29:06