All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Jeff Layton <jtlayton@poochiereds.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: making the 'addr=' mount option an address hint
Date: Sun, 17 Jul 2005 18:51:44 +0200	[thread overview]
Message-ID: <20050717165143.GD22503@suse.de> (raw)
In-Reply-To: <1121614708.6713.41.camel@localhost.localdomain>

On Sun, Jul 17, 2005 at 11:38:28AM -0400, Jeff Layton wrote:
>   Unfortunately, I've found that when the mount program does a
> gethostbyname() call to get the address of the host, it simply picks the
> first address in the list, without regard for how "close" it is to the
> client.
> 
> The upshot of this is that if even autofs picks a replicated mount entry
> that is on the same subnet as the client, we may end up mounting across
> a router anyway.

Yes, I think this is why the am-utils automounter of old had all these
weird syntax additions to give you control over which server a client
ends up selecting.

> So, what I'd like to do is roll a patch for mount to change the behavior
> of the 'addr=' option. Instead of ignoring it, we'd treat it as an
> address hint. If one of the addresses returned by gethostbyname()
> matches this address, then we'd mount using that address. Otherwise, the
> existing behavior would prevail (use the first address in the list).

Why just use it as a hint? Why not override address resolution completely
when addr= is given?

Olaf
-- 
Olaf Kirch   |  --- o --- Nous sommes du soleil we love when we play
okir@suse.de |    / | \   sol.dhoop.naytheet.ah kin.ir.samse.qurax


-------------------------------------------------------
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

  reply	other threads:[~2005-07-17 16:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-17 15:38 making the 'addr=' mount option an address hint Jeff Layton
2005-07-17 16:51 ` Olaf Kirch [this message]
2005-07-17 17:40   ` Jeff Layton
2005-07-18 15:22   ` Trond Myklebust
2005-07-18 17:55     ` Jeff Layton
2005-07-18 18:09       ` Dan Stromberg
2005-07-18 18:45         ` Trond Myklebust
2005-07-18 19:59         ` Jeff Layton
2005-07-18 15:36 ` Trond Myklebust
2005-07-18 18:24   ` [NFS] " Jeff Layton
2005-07-18 18:37     ` Trond Myklebust
2005-07-18 18:37       ` Trond Myklebust
2005-07-18 19:54       ` Olaf Kirch
2005-07-18 20:49         ` Trond Myklebust
2005-07-18 20:49           ` Trond Myklebust
2005-07-19 12:26           ` Ian Kent
2005-07-19 12:22         ` [NFS] " Ian Kent
2005-07-19 12:17     ` Ian Kent
2005-07-19 12:03   ` Ian Kent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050717165143.GD22503@suse.de \
    --to=okir@suse.de \
    --cc=jtlayton@poochiereds.net \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.