From: Neil Brown <neilb@suse.de>
To: Peng Yu <pengyu.ut@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Does the machine need to be restarted after RPCNFSDCOUNT in /etc/default/nfs-kernel-server (ubuntu) is edited?
Date: Fri, 27 Aug 2010 07:43:39 +1000 [thread overview]
Message-ID: <20100827074339.605f58c7@notabene> (raw)
In-Reply-To: <AANLkTincnCeQYi6fvbEHLqqz+gYp0_ETdPAq6QebOxDg@mail.gmail.com>
On Thu, 26 Aug 2010 06:59:16 -0500
Peng Yu <pengyu.ut@gmail.com> wrote:
> On Wed, Aug 25, 2010 at 6:36 PM, Neil Brown <neilb@suse.de> wrote:
> > On Wed, 25 Aug 2010 15:02:14 -0500
> > Peng Yu <pengyu.ut@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> I changed the value of RPCNFSDCOUNT in /etc/default/nfs-kernel-server
> >> (ubuntu). Do I need to restart the machine?
> >>
> >> Or I need to restart nfsd? If so, would you please let me know how to
> >> restart nfsd?
> >>
> >
> > Easiest thing to do is simply
> >
> > rpc.nfsd $NUMBER
> >
> > it will change the number of running threads to match the number that you
> > give.
>
> This will change the number in /etc/default/nfs-kernel-server? Or it
> will not, meaning if I reboot machine, there will still be an old
> number of nfsd running?
>
Try it an see ???
No, it doesn't change any file. It just changes the number of running
threads.
If you want to change the number of threads at next reboot, change the file.
If you want to change the number of threads running now, run the command.
If you want to do both, do both.
NeilBrown
prev parent reply other threads:[~2010-08-26 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 20:02 Does the machine need to be restarted after RPCNFSDCOUNT in /etc/default/nfs-kernel-server (ubuntu) is edited? Peng Yu
2010-08-25 23:11 ` sfaibish
2010-08-25 23:36 ` Neil Brown
2010-08-26 0:12 ` sfaibish
2010-08-26 0:31 ` Neil Brown
2010-08-26 10:17 ` sfaibish
2010-08-26 10:42 ` Neil Brown
2010-08-26 11:59 ` Peng Yu
2010-08-26 21:43 ` Neil Brown [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=20100827074339.605f58c7@notabene \
--to=neilb@suse.de \
--cc=linux-nfs@vger.kernel.org \
--cc=pengyu.ut@gmail.com \
/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