From: Rudi Starcevic <tech@wildcash.com>
To: nfs@lists.sourceforge.net
Subject: Rpc.statd max threads
Date: Wed, 06 Apr 2005 12:57:50 -0700 [thread overview]
Message-ID: <42543F3E.1080300@wildcash.com> (raw)
Hi,
I'm using a FreeBSD NFS server with Linux NFS clients.
I am having trouble finding how to set the minimum or maximum or default
client connection threads.
I can increase my nfsd on FreeBSD to 20 and would like now to up the
clients on Linux.
Man rpc.statd doesn't seem to show me how.
Can you please help?
This is the output from man rpc.statd on my Debian Linux box
-F
By default, rpc.statd forks and puts itself in the background when
started. The -F argument tells it to
remain in the foreground. This option is mainly for debugging purposes.
-d
By default, rpc.statd sends logging messages via syslog(3) to system
log. The -d argument forces it to log
verbose output to stderr instead. This option is mainly for
debugging purposes, and may only be used in
conjunction with the -F parameter.
-n, --name name
specify a name for rpc.statd to use as the local hostname. By default,
rpc.statd will call gethostname(2)
to get the local hostname. Specifying a local hostname may be useful for
machines with more than one inter-faces.
-o, --outgoing-port port
specify a port for rpc.statd to send outgoing status requests from.
By default, rpc.statd will ask
portmap(8) to assign it a port number. As of this writing, there
is not a standard port number that
portmap always or usually assigns. Specifying a port may be useful when
implementing a firewall.
-p, --port port
specify a port for rpc.statd to listen on. By default, rpc.statd will
ask portmap(8) to assign it a port
number. As of this writing, there is not a standard port number that
portmap always or usually assigns.
Specifying a port may be useful when implementing a firewall.
-P, --state-directory-path directory
specify a directory in which to place statd state information. If this
option is not specified the default
of /var/lib/nfs is used.
-N
Causes statd to run in the notify-only mode. When started in this
mode, the statd program will check its
state directory, send notifications to any monitored nodes, and exit
once the notifications have been sent.
This mode is used to enable Highly Available NFS implementations (i.e.
HA-NFS).
-? Causes rpc.statd to print out command-line help and exit.
-V Causes rpc.statd to print out version information and exit.
Thank you.
Regards,
Rudi
-------------------------------------------------------
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
reply other threads:[~2005-04-06 2:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42543F3E.1080300@wildcash.com \
--to=tech@wildcash.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