From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: nfs@lists.sourceforge.net
Subject: Random UDP port assignment for rpc.statd
Date: Sun, 20 Feb 2005 12:13:12 +0100 [thread overview]
Message-ID: <20050220111312.GA3974@s> (raw)
Why isn't it possible to specify all of statd's listening ports
using the -p flag? It works for the TCP port and one of the
UDP ports, but there is always one more listening UDP port that
is randomly assigned. I googled around for information on this
problem, and came up with this Debian bug report:
http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg11985.html
The thread ends with "I think we may have a real bug", but this
was reported in 1.0.6, and the problem still persists in 1.0.7,
so I was wondering if this isn't a bug after all.
Btw, there's also a similar problem with nfsd: In addition to
the standard listening port at 2049, it always opens a random
port in the high port range (32000-32768 or something like that).
In case it matters: I'm using Linux 2.6.10 and Slackware 10.1.
--
Haakon
-------------------------------------------------------
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 reply other threads:[~2005-02-20 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 11:13 Haakon Riiser [this message]
2005-02-20 14:03 ` Random UDP port assignment for rpc.statd Trond Myklebust
2005-02-20 14:10 ` Haakon Riiser
2005-02-20 15:30 ` Trond Myklebust
2005-02-20 16:43 ` Trond Myklebust
2005-02-20 17:04 ` Haakon Riiser
2005-02-28 3:21 ` Neil Brown
2005-02-20 17:21 ` Haakon Riiser
2005-02-20 17:38 ` Trond Myklebust
2005-02-20 18:01 ` Haakon Riiser
2005-02-28 3:32 ` Sven Köhler
2005-02-28 23:53 ` Dan Stromberg
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=20050220111312.GA3974@s \
--to=haakon.riiser@fys.uio.no \
--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