From: Steve Dickson <SteveD@RedHat.com>
To: Greg Banks <gnb@melbourne.sgi.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH] SGI 904217 (2/2): allow enabling TCP without recompile
Date: Mon, 15 Dec 2003 21:00:40 -0500 [thread overview]
Message-ID: <3FDE6748.7090404@RedHat.com> (raw)
In-Reply-To: <3FDD6D78.A8FE3262@melbourne.sgi.com>
Greg Banks wrote:
>These two patches Linux systems to be shipped with CONFIG_NFSD_TCP=y
>but TCP support disabled at runtime until the sysadmin edits the
>/etc/sysconfig/nfs file and restarts NFS. The idea is that TCP
>support is still disabled by default, but can be enabled with less
>pain than currently is the case (we have customers who want to try
>it).
>
>
Why disable it? Since UPD is still mountd's default transport..
>The second patch is for nfs-utils and adds a -t option to nfsd which
>uses the new nfsctl (added in the first patch) to enable specific
>transports, and the infrastructure to allow the sysadmin to specify
>it easily. Default is to enable UDP only for compatibility.
>
>
This seems a bit messy.... Why not just turn on TCP and have
nfsd listen on both types of transports?
SteveD.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-12-16 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 8:14 [PATCH] SGI 904217 (2/2): allow enabling TCP without recompile Greg Banks
2003-12-16 2:00 ` Steve Dickson [this message]
2003-12-16 2:16 ` Greg Banks
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=3FDE6748.7090404@RedHat.com \
--to=steved@redhat.com \
--cc=gnb@melbourne.sgi.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.