From mboxrd@z Thu Jan 1 00:00:00 1970 From: "michael@kmaclub.com" Subject: Re: autofs changes process's current working directory Date: Mon, 14 Dec 2009 15:07:54 -0700 Message-ID: <4B26B73A.3030402@kmaclub.com> References: <4ACED0F1.9050909@themaw.net> <4B268068.1030704@themaw.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B268068.1030704@themaw.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: autofs-bounces@linux.kernel.org Errors-To: autofs-bounces@linux.kernel.org Content-Type: text/plain; charset="us-ascii"; format="flowed" To: autofs@linux.kernel.org On 12/14/2009 11:14 AM, Ian Kent wrote: > 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. Hi Ian, Are you aware of any work to back port these changes into ~2.6.16? I am using an enterprise distribution and this issue is causing us problems. Michael