From: Olaf Kirch <okir@suse.de>
To: "ian sison (mailing list)" <ian.s@qsr.com.ph>
Cc: nfs@lists.sourceforge.net
Subject: Re: Reserving port 800 on linux NFS clients
Date: Wed, 17 Mar 2004 09:33:10 +0100 [thread overview]
Message-ID: <20040317083309.GA14278@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0403171349300.20810-100000@jeprox.qsr.com.ph>
On Wed, Mar 17, 2004 at 01:50:08PM +0800, ian sison (mailing list) wrote:
> I think http://www.lowth.com/LinWiz/nfs_help.html would be helpful in
> this.
I don't think it will help, because this document covers server side
port allocation. The question was about the NFS client port allocation.
The NFS currently allocates a reserved port for the NFS client
by trying all ports from 800 downward, until it finds one it can
bind to.
There are two ways to make the client skip port 800.
- start your network service before mounting any NFS file
systems. When NFS tries to bind a reserved port, it
will find this one is already in use and skip it
- if that is not possible, you need to patch net/sunrpc/xprt.c
and change the XPRT_MAX_RESVPORT define to e.g. 799
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2004-03-17 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 4:36 Reserving port 800 on linux NFS clients Errol Casey
2004-03-17 5:50 ` ian sison (mailing list)
2004-03-17 8:33 ` Olaf Kirch [this message]
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=20040317083309.GA14278@suse.de \
--to=okir@suse.de \
--cc=ian.s@qsr.com.ph \
--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.