>From [EMAIL PROTECTED] Thu Feb 15 02:14:25 2001
>Return-Path: <[EMAIL PROTECTED]>
Received: from hera.kernel.org (IDENT:[EMAIL PROTECTED] [209.10.217.83])
by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id CAA24184
for <[EMAIL PROTECTED]>; Thu, 15 Feb 2001 02:14:23 +0900
Received: (from majordom@localhost)
by hera.kernel.org (8.9.3/8.9.3) id IAA25522
for autofs-list; Wed, 14 Feb 2001 08:26:09 -0800
Received: from gw.goop.org ([EMAIL PROTECTED]
[206.170.148.147])
by hera.kernel.org (8.9.3/8.9.3) with ESMTP id IAA25519
for <[EMAIL PROTECTED]>; Wed, 14 Feb 2001 08:26:09 -0800
Received: from ixodes.goop.org (ixodes [192.168.0.5])
by gw.goop.org (Postfix) with ESMTP
id 080E562002; Wed, 14 Feb 2001 08:26:06 -0800 (PST)
Received: by ixodes.goop.org (Postfix, from userid 0)
id DD3ED104B6; Wed, 14 Feb 2001 08:26:05 -0800 (PST)
Date: Wed, 14 Feb 2001 08:26:05 -0800
From: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
To: Patrick Schemitz <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED],
Administration of EKP Cluster <[EMAIL PROTECTED]>
Subject: Re: It works... at the _second_ try
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <[EMAIL PROTECTED]>; from
[EMAIL PROTECTED] on Wed, Feb 14, 2001 at 12:23:41PM +0100
Sender: [EMAIL PROTECTED]
Precedence: bulk
Status: O
Content-Length: 1414
Lines: 33
On Wed, Feb 14, 2001 at 12:23:41PM +0100, Patrick Schemitz wrote:
> Hi,
>
> I'm just trying to set up autofs 4.0.0pre9 (as it comes with brand new
> SuSE 7.1) for our network and ran into a problem:
>
> What I want to do is crossmounting all the home directories of our
> Linux machines (twenty-something boxes) with a nifty wildcard map,
> via NFS. In principle this is working great, the map is a fraction
> of the old AMD map, and the mounter mounts as expected, but...
>
> When I try to "ls" a formerly unmounted directory (or "cat" a file
> on a formerly unmounted directory, it works fine... AT THE SECOND
> TRY. For the first try, it gives "No such file or directory". When
> I redo the command (from history) a second later, it works as
> expected!
>
> Interesting enough, the "cd" command works instantaniously.
>
> We're running a lot of automated jobs which write on network volumes
> and which, unfortunately, are not very forgiving about non-existant
> directories. So my question is: is there a way (an option?) to halt
> the program which demands the mount until the FS is really mounted?
That's supposed to happen, but there's some subtle synchonization stuff
going on which often gets broken by other kernel changes. The
confusing thing is that I've seen this with some servers and not others;
I don't know what the difference is.
What's your kernel version, server type, etc?
Thanks,
J
