Hi Michael, (the following holds for both autofs v4 and v5)
usually the daemon creates these directories on startup and removes them on exit. If you do not want that to happen, it suffices to mark the directory as u-w: ] r...@apocatequil:/etc# grep ^/misc /etc/auto.master ] /misc /etc/auto.misc ] r...@apocatequil:/etc# ls -ld /misc ] ls: cannot access /misc: No such file or directory ] r...@apocatequil:/etc# /etc/init.d/autofs start ] Starting automount: done. ] r...@apocatequil:/etc# ls -ld /misc ] drwxr-xr-x 2 root root 0 2009-07-25 16:08 /misc ] r...@apocatequil:/etc# /etc/init.d/autofs stop ] Stopping automount: done. ] r...@apocatequil:/etc# ls -ld /misc ] ls: cannot access /misc: No such file or directory ] r...@apocatequil:/etc# mkdir /misc; chmod 0555 /misc ] r...@apocatequil:/etc# ls -ld /misc ] dr-xr-xr-x 2 root root 4096 2009-07-25 16:08 /misc ] r...@apocatequil:/etc# /etc/init.d/autofs start ] Starting automount: done. ] r...@apocatequil:/etc# ls -ld /misc ] drwxr-xr-x 2 root root 0 2009-07-25 16:08 /misc ] r...@apocatequil:/etc# /etc/init.d/autofs stop ] Stopping automount: done. ] r...@apocatequil:/etc# ls -ld /misc ] dr-xr-xr-x 2 root root 4096 2009-07-25 16:08 /misc ] r...@apocatequil:/etc# So I presume the real problem here is that autofs cannot create the /net mountpoint upon startup. This is not a very usual case, because the only possibility I can think of is a NFS root with root squashing enabled (but how can it remove that directory then when it's going down?)... I'm not sure if this justifies "grave". But I admit that it's not in the documentation (at least nowhere I know of) and that the initscript startup exit code is not helpful. Regards, Jan
signature.asc
Description: Digital signature
