From: Max Matveev Subject: Re: Difference in behaviour between 4.1.3 and 4.1.4 Date: 03 Aug 2005 18:13:30 +1000 Message-ID: References: <17135.29013.324264.704045@segfault.boston.redhat.com> <17135.30311.969737.212368@kuku.melbourne.sgi.com> Mime-Version: 1.0 Return-path: Sender: max.matveev@sgi.com In-Reply-To: <17135.30311.969737.212368@kuku.melbourne.sgi.com> 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" Content-Transfer-Encoding: 7bit To: jmoyer@redhat.com Cc: autofs@linux.kernel.org >>>>> "makc" == Max Matveev writes: >>>>> "jmoyer" == Jeff Moyer writes: jmoyer> I have never seen this issue. I haven't seen it in the jmoyer> upstream autofs package nor in any variant of the Red Hat jmoyer> packages with which I work. makc> Dang! I was hopeing it was a known issue and I wouldn't have to dive makc> into the code - apparently 4.0.0-pre-something on Mandrake behave makc> similarly. Maybe it's a kernel module issue, not the user-space makc> automounter one. Scrap that - happened to be a mismatch between kernel and user space: kernel at autofs3, userspace at autofs4, modprobe.conf got clobbered during update. max