Leonardo Chiquitto wrote: >>> I'm experiencing a problem with autofs. It seems that when a process >>> is inside an automounted nfs filesystem, if I restart the automount >>> daemon the current working directory of the process is changed and a >>> few leading directory are removed leading to a non-existent cwd. >> That's right. >> >> It's because, with older user space and kernel, the mount is detached >> from the mount tree by a "umount -l" at restart when trying to cleanup >> stale mounts. >> >> Note that this is a non-trivial problem and took a long time to fix. >> >> What autofs and kernel are you using? > > Ian, > > I'm also getting this problem on 2.6.31 with autofs-5.0.4. Please, do you > remember when the fix was committed? Is this related to some (new) > configuration option?
Have a look at your init script and the installed autofs configuration. Basically you need /dev/autofs to exist (created when the autofs4 kernel module is loaded) and that's about it. But the init script may be removing it because it thinks you don't want to use it. Ian _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
