From: Steve Dickson <SteveD@redhat.com>
To: Chip Salzenberg <chip@pobox.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, nfs@lists.sourceforge.net
Subject: Re: [KNFSD] [PATCH] fixed '-p port' arg to rpc.nfsd plus more.
Date: Mon, 21 Mar 2005 11:22:38 -0500 [thread overview]
Message-ID: <423EF4CE.90501@RedHat.com> (raw)
In-Reply-To: <20050321154645.GE1736@perlsupport.com>
Chip Salzenberg wrote:
> According to Steve Dickson:
>
>> -N or --no-nfs-version vers
>> This option can be used to request that rpc.nfsd does not offer
>> certain versions of NFS. The current version of rpc.nfsd can
>> support both NFS version 2,3 and the newer version 4.
>
>
> Thanks very much for the patches, but would you please add on support
> for the '-V' flag specifying the versions that should be allowed?
Well since everything is on by default, I figured all that
was needed was a way to turn things off, but it would
be a non-issue to add.
>
>
>> -T or --no-tcp
>> Disable rpc.nfsd from accepting TCP connections from clients.
>>
>> -U or --no-udp
>> Disable rpc.nfsd from accepting UDP connections from clients.
>
>
> And could you please document when (if ever) these options would be
> useful to an end user?
I was thinking servers behind firewalls might want to
explicitly define one protocol or the other, just
to keep things simple and I know other servers have
these options.
steved.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-03-21 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 14:42 [kNFSD] [PATCH] fixed '-p port' arg to rpc.nfsd plus more Steve Dickson
2005-03-21 14:56 ` J. Bruce Fields
2005-03-21 15:18 ` Trond Myklebust
2005-03-21 15:59 ` Steve Dickson
2005-03-21 15:46 ` [KNFSD] " Chip Salzenberg
2005-03-21 16:22 ` Steve Dickson [this message]
2005-03-21 16:39 ` Chip Salzenberg
2005-03-21 23:34 ` [kNFSD] " Neil Brown
2005-03-22 10:17 ` Steve Dickson
2005-03-22 12:27 ` Steve Dickson
2005-03-22 13:10 ` Steve Dickson
2005-03-22 15:01 ` Steve Dickson
2005-03-23 11:56 ` Steve Dickson
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=423EF4CE.90501@RedHat.com \
--to=steved@redhat.com \
--cc=chip@pobox.com \
--cc=neilb@cse.unsw.edu.au \
--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.