From: Haakon Riiser <haakon.riiser@fys.uio.no>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: Random UDP port assignment for rpc.statd
Date: Sun, 20 Feb 2005 19:01:20 +0100 [thread overview]
Message-ID: <20050220180120.GA702@s> (raw)
In-Reply-To: <1108921114.27120.51.camel@lade.trondhjem.org>
[Trond Myklebust]
> su den 20.02.2005 Klokka 18:21 (+0100) skreiv Haakon Riiser:
>> I almost forgot this one. Does nfsd's mystery UDP port have
>> the same purpose as the one from statd, i.e. communication
>> with the portmapper?
> [...]
> The lockd daemon needs an extra port, but you can control that
> (and this control mechanism _should_ work) using the pseudofiles
> in /proc/sys/fs/nfs, or the kernel parameters lockd.udpport
> and lockd.tcpport.
Thanks, this works when I prefix udpport and tcpport with "nlm_".
But I see you already know that: :-)
http://www.ussg.iu.edu/hypermail/linux/kernel/0403.3/1915.html
--
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 prev parent reply other threads:[~2005-02-20 18:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 11:13 Random UDP port assignment for rpc.statd Haakon Riiser
2005-02-20 14:03 ` 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 [this message]
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=20050220180120.GA702@s \
--to=haakon.riiser@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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