All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: nfs <nfs@lists.sourceforge.net>
Subject: Re: proc/sys/sunrpc/max_resvport
Date: Tue, 09 Oct 2007 17:01:58 -0400	[thread overview]
Message-ID: <1191963718.3697.2.camel@pc.ilinx> (raw)
In-Reply-To: <1191963460.7052.1.camel@heimdal.trondhjem.org>


[-- Attachment #1.1: Type: text/plain, Size: 565 bytes --]

On Tue, 2007-10-09 at 16:57 -0400, Trond Myklebust wrote:
> 
> No. The portmapper is a userland process and has nothing to do
> with /proc/sys/sunrpc/max_resvport.

No wonder I couldn't find the linkage.  :-)

> The latter controls the kernel's sunrpc client port usage _only_.

Hrm.  So that would mean only kernel space rpc services, like nfsd?

I guess there is no way to limit the userspace portmapper the way
max_resvport does for the kernel rpc services then?

b.

-- 
My other computer is your Microsoft Windows server.

Brian J. Murrell

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 314 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-10-09 21:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 17:12 proc/sys/sunrpc/max_resvport Brian J. Murrell
2007-10-09 20:57 ` proc/sys/sunrpc/max_resvport Trond Myklebust
2007-10-09 21:01   ` Brian J. Murrell [this message]
2007-10-09 21:09     ` proc/sys/sunrpc/max_resvport Trond Myklebust
2007-10-09 21:26       ` proc/sys/sunrpc/max_resvport Brian J. Murrell
2007-10-09 23:43         ` proc/sys/sunrpc/max_resvport Trond Myklebust
2007-10-10 15:10           ` proc/sys/sunrpc/max_resvport Brian J. Murrell
2007-10-11 13:44             ` proc/sys/sunrpc/max_resvport Trond Myklebust
2007-10-11 13:53               ` proc/sys/sunrpc/max_resvport Brian J. Murrell

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=1191963718.3697.2.camel@pc.ilinx \
    --to=brian@interlinx.bc.ca \
    --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.