From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@redhat.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 3/3] nfs-utils: add IPv6 support to nfsd
Date: Mon, 18 May 2009 11:42:38 -0400 [thread overview]
Message-ID: <4A1181EE.7080401@RedHat.com> (raw)
In-Reply-To: <00A26259-D5D8-4E1C-91F4-6AB5CE194870@oracle.com>
Chuck Lever wrote:
> On May 11, 2009, at 1:58 PM, Jeff Layton wrote:
>> Add 2 new options to rpc.nfsd -- -4 and -6. -4 makes it an IPv4-only
>> server, and -6 makes it IPv6-only. Restructure the -H option so that
>> if the address appears to be or resolves to an IPv4 address, that
>> IPv6 is disabled. Ditto if it resolves to an IPv6 address.
>
> For rpc.statd, I'm following Olaf's suggestion to use /etc/netconfig to
> decide what transports to use for listeners. Basically, rpc.statd
> attempts to start listeners for all visible netids (marked with 'v') in
> /etc/netconfig. This is how Solaris works, as I understand it. I'm
> planning to take this course for rpc.mountd as well.
>
> Maybe rpc.nfsd should follow suit?
I would have to agree... Jeff, what do you think?
steved.
next prev parent reply other threads:[~2009-05-18 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 17:58 [PATCH 0/3] nfs-utils: add IPv6 support to rpc.nfsd (RFC) Jeff Layton
2009-05-11 17:58 ` [PATCH 1/3] nfs-utils: rearrange nfssvc.c Jeff Layton
2009-05-11 17:58 ` [PATCH 2/3] nfs-utils: set IPV6_V6ONLY on nfssvc IPv6 sockets Jeff Layton
2009-05-11 17:58 ` [PATCH 3/3] nfs-utils: add IPv6 support to nfsd Jeff Layton
2009-05-11 19:34 ` Chuck Lever
2009-05-18 15:42 ` Steve Dickson [this message]
[not found] ` <4A1181EE.7080401-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-05-18 15:48 ` Jeff Layton
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=4A1181EE.7080401@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@redhat.com \
--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.