From: Neil Horman <nhorman@redhat.com>
To: naveen a <naveen2005@india.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Help needed in understanding port allocation in NFS
Date: Wed, 16 Feb 2005 08:14:40 -0500 [thread overview]
Message-ID: <42134740.4050700@redhat.com> (raw)
In-Reply-To: <20050216102547.A248323CFA@ws5-3.us4.outblaze.com>
naveen a wrote:
> Hi,
>
> I wanted some info related to port selection in NFS.
>
> What happens when the port number is not specified in the command line switch or configuration
>
> file for mountd and statd?
>
> In man pages it is mentioned as statd/mountd will select the port from portmapper.
>
> Can you please let me know how a port is allotted and the code path in source.
>
Thats really the entire point of the portmapper. When userspace service
are started up, there is not preset port which is allocated. The new
rpc service opens a socket and binds to a system selected port (using
bindresvport IIRC). That port value is then registered witht he
portmapper. The portmapper always listens on the sunrpc port (port 111
I think), so that remote clients can query the portmapper daemon for
which port to connect to to get a specific service.
HTH
Neil
--
/***************************************************
*Neil Horman
*Software Engineer
*Red Hat, Inc.
*nhorman@redhat.com
*gpg keyid: 1024D / 0x92A74FA1
*http://pgp.mit.edu
***************************************************/
-------------------------------------------------------
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
prev parent reply other threads:[~2005-02-16 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 10:25 Help needed in understanding port allocation in NFS naveen a
2005-02-16 13:14 ` Neil Horman [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=42134740.4050700@redhat.com \
--to=nhorman@redhat.com \
--cc=naveen2005@india.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox