From: Ian Kent <raven@themaw.net>
To: Jeff Mahoney <jeffm@suse.com>, autofs@vger.kernel.org
Subject: Re: mount -oaddr=<ipaddr> ?
Date: Tue, 05 Apr 2016 11:12:29 +0800 [thread overview]
Message-ID: <1459825949.4090.10.camel@themaw.net> (raw)
In-Reply-To: <57030D04.7010805@suse.com>
On Mon, 2016-04-04 at 20:55 -0400, Jeff Mahoney wrote:
> Hi all -
>
> I'm investigating an issue where our user updated from SLE11 to SLE12
> and the hostname for autofs mounts stopped appearing in the 'mount'
> output. I know why this happens, what the reason for it being this
> way
> is, and that it can be overridden by setting the
> use_hostname_for_mounts=yes option (and the side effects). Before I
> go
> and write up the patch implementing it, is there a reason why autofs
> doesn't pass the hostname in the mount source and specify the ip
> address
> using the -oaddr=<ipaddr> option? Was this tried and found to be
> wanting somehow?
TBH I didn't even consider doing that.
But the daemon needs to be conservative in the options it uses because
maps may be used with other platforms and unknown or non-standard
options can cause mount failures.
While Linux mount.nfs(8) has the sloppy option (which maintainers seem
to try and remove from time to time) other platforms probably don't.
The addr=<address> option isn't listed as a valid option in nfs(5) and
neither is it listed in on-line Solaris documentation that I could find
so I'm not sure making the daemon use it is a good idea.
Maybe there's another way...
Note that I do need to be able to mount to a specific IP address while
specifying the host name in the mount command but don't know of a way todo it.
>
> Thanks,
>
> -Jeff
>
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
next prev parent reply other threads:[~2016-04-05 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 0:55 mount -oaddr=<ipaddr> ? Jeff Mahoney
2016-04-05 3:12 ` Ian Kent [this message]
2016-04-05 13:18 ` Jeff Mahoney
2016-04-08 0:21 ` 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=1459825949.4090.10.camel@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=jeffm@suse.com \
/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.