From: NeilBrown <neilb@suse.com>
To: Ian Kent <raven@themaw.net>, autofs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] autofs 5.1.2 release
Date: Wed, 20 Dec 2017 14:29:59 +1100 [thread overview]
Message-ID: <876092krew.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <1465960537.3164.1.camel@themaw.net>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
Hi Ian,
I've been looking at:
> - add configuration option to use fqdn in mounts.
(commit 9aeef772604) because using this new option causes a regression.
If you are using the "replicated server" functionality, then
use_hostname_for_mounts = yes
completely disables it.
This is caused by:
diff --git a/modules/replicated.c b/modules/replicated.c
index 32860d5fe245..8437f5f3d5b2 100644
--- a/modules/replicated.c
+++ b/modules/replicated.c
@@ -667,6 +667,12 @@ int prune_host_list(unsigned logopt, struct host **list,
if (!*list)
return 0;
+ /* If we're using the host name then there's no point probing
+ * avialability and respose time.
+ */
+ if (defaults_use_hostname_for_mounts())
+ return 1;
+
/* Use closest hosts to choose NFS version */
My question is: why what this particular change made.
Why can't prune_host_list() be allowed to do it's thing
when use_hostname_for_mounts is set.
I understand that it would be pointless choosing between
the different interfaces of a multi-homed host, but there is still value
in choosing between multiple distinct hosts.
What, if anything, might go wrong if I simply reverse this chunk of the
patch?
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-12-20 3:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 3:15 [ANNOUNCE] autofs 5.1.2 release Ian Kent
2017-12-20 3:29 ` NeilBrown [this message]
2017-12-20 5:52 ` Ian Kent
2017-12-20 6:10 ` Ian Kent
2017-12-20 6:50 ` Ian Kent
2017-12-21 1:09 ` NeilBrown
2017-12-21 11:06 ` Ian Kent
2017-12-21 11:36 ` Ian Kent
2018-01-02 22:14 ` NeilBrown
2018-01-18 1:15 ` Ian Kent
2018-01-18 2:19 ` Ian Kent
2017-12-20 7:30 ` 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=876092krew.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=raven@themaw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).