From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: making the 'addr=' mount option an address hint
Date: Mon, 18 Jul 2005 14:37:50 -0400
Message-ID: <1121711870.8707.5.camel@lade.trondhjem.org>
References: <1121614708.6713.41.camel@localhost.localdomain>
	 <1121700961.8780.13.camel@lade.trondhjem.org>
	 <1121711065.23863.31.camel@barsoom.rdu.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Cc: nfs@lists.sourceforge.net, autofs@linux.kernel.org
To: Jeff Layton <jtlayton@poochiereds.net>
In-Reply-To: <1121711065.23863.31.camel@barsoom.rdu.redhat.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

m=C3=A5 den 18.07.2005 Klokka 14:24 (-0400) skreiv Jeff Layton:
> On Mon, 2005-07-18 at 11:36 -0400, Trond Myklebust wrote:
> > There's nothing preventing it from working, but what is stopping you
> > from developing a fully automatic version?
>=20
> Nothing is stopping that, but if we're going to do so much in the mount
> program, there's probably no point in doing all of this in autofs. Why
> do RPC pings at all in autofs if we're going to turn right around and do
> them again in the mount program? For mounting over a WAN (for instance)
> the ping checks could really add up to a substantial delay in mounting.

I would not at all support doing this sort of thing in autofs. If it is
to be done, it should be done by the mount program.

Cheers,
 Trond


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs