From: Neil Brown <neilb@suse.de>
To: Jason Keltz <jas@cse.yorku.ca>
Cc: linux-nfs@vger.kernel.org
Subject: Re: exporting to a list of IPs
Date: Wed, 4 Aug 2010 13:45:27 +1000 [thread overview]
Message-ID: <20100804134527.146397ff@notabene> (raw)
In-Reply-To: <4C583B63.4050903@cse.yorku.ca>
On Tue, 03 Aug 2010 11:53:07 -0400
Jason Keltz <jas@cse.yorku.ca> wrote:
> Hi.
>
> Why is it that you cannot NFS export to a list of IPs and have exportfs
> leave the list of IPs in etab without converting over to FQDN?
My memory is that if you only list IP addresses in /etc/exports then it will
do just want you want. But if you list any host names or net groups then it
has to do a DNS lookup on everything to see if either of those matches.
>
> In Changelog:
>
> 2001-09-20 NeilBrown <neilb@cse.unsw.edu.au>
> Anne Milicia <milicia@missioncriticallinux.com>
>
> * support/export/client.c (client_lookup) call gethostbyadd
> to make sure that we have a canonical hostname, even for
> dotted-quads
I think this patch only related to netgroup lookups.
>
> Why does mountd need to repeat the gethostbyname() lookup on every host
> even though exportfs already converted over to using hostname?
exportfs doesn't convert over host hostnames. It essentially
copies /etc/exports to /var/lib/nfs/etab with minor formatting changes.
What do you actually put in /etc/exports, what do you find
in /var/lib/nfs/etab, and what exactly is the problem?
NeilBrown
>
> Thanks,
>
> Jason.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-04 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 15:53 exporting to a list of IPs Jason Keltz
2010-08-04 3:45 ` Neil Brown [this message]
2010-08-04 13:47 ` Jason Keltz
2010-08-04 22:13 ` Neil Brown
2010-08-06 1:42 ` Jason Keltz
2010-08-06 4:26 ` Neil Brown
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=20100804134527.146397ff@notabene \
--to=neilb@suse.de \
--cc=jas@cse.yorku.ca \
--cc=linux-nfs@vger.kernel.org \
/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.