From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Add config to nfsd to set number of threads
Date: Thu, 17 Dec 2015 21:04:24 +0100 [thread overview]
Message-ID: <20151217200424.GC3653@free.fr> (raw)
In-Reply-To: <1450381505-3796-1-git-send-email-universeII@gmx.de>
Andreas, All,
On 2015-12-17 20:45 +0100, Andreas Ehmanns spake thusly:
> Signed-off-by: Andreas Ehmanns <universeII@gmx.de>
I forgot in my previous reply, but subject should have been:
package/nfsd: accept config to set number of threads
This can be fixed by a maintainer when he applies, so no need to
resubmit...
Otherwise:
Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Unrelated yto this change, I noticed that this script is completely
consistent with how it stops services:
- sometimes, we killall, sometimes we kill-9
- the order in which we kill, echo and rm pid file is not consistent
It would be nice if we stopped all the NFS services in a consistent way,
like always use killall, then remove the pid file, and eventually echo
the status. Would you like to send a follow-up patch that does that
cleanup, please? ;-)
Regards,
Yann E. MORIN.
> ---
> package/nfs-utils/S60nfs | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/package/nfs-utils/S60nfs b/package/nfs-utils/S60nfs
> index ec7c909..5639b8f 100755
> --- a/package/nfs-utils/S60nfs
> +++ b/package/nfs-utils/S60nfs
> @@ -13,6 +13,14 @@ mkdir -p /run/nfs/sm
> mkdir -p /run/nfs/sm.bak
> touch /run/nfs/rmtab
>
> +CFG_FILE=/etc/default/nfsd
> +
> +NR_THREADS=2
> +if [ -f "${CFG_FILE}" ]; then
> + . "${CFG_FILE}"
> +fi
> +
> +
> start() {
> # Start daemons.
> printf "Starting NFS statd: "
> @@ -25,7 +33,7 @@ start() {
> echo "done"
>
> printf "Starting NFS daemon: "
> - rpc.nfsd 2
> + rpc.nfsd ${NR_THREADS}
> echo "done"
>
> printf "Starting NFS mountd: "
> @@ -40,7 +48,7 @@ stop() {
> killall -q rpc.mountd
> echo "done"
>
> - echo "Shutting down NFS daemon: "
> + printf "Shutting down NFS daemon: "
> kill -9 `pidof nfsd` 2>/dev/null
> echo "done"
>
> --
> 2.1.4
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-12-17 20:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 19:45 [Buildroot] [PATCH 1/1] Add config to nfsd to set number of threads Andreas Ehmanns
2015-12-17 20:04 ` Yann E. MORIN [this message]
2015-12-17 20:14 ` Andreas Ehmanns
2015-12-17 20:25 ` Yann E. MORIN
2015-12-17 20:26 ` Andreas Ehmanns
2016-02-04 8:31 ` Andreas Ehmanns
2016-02-04 20:50 ` Yann E. MORIN
2016-02-12 9:31 ` Andreas Ehmanns
2016-02-25 20:40 ` Andreas Ehmanns
2016-02-25 23:30 ` Arnout Vandecappelle
2016-04-15 8:37 ` Andreas Ehmanns
2016-04-15 9:00 ` Arnout Vandecappelle
2016-04-15 9:09 ` Andreas Ehmanns
2016-04-15 9:23 ` Arnout Vandecappelle
2015-12-17 20:52 ` Thomas Petazzoni
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=20151217200424.GC3653@free.fr \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.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