From: Phil Blundell <pb@pbcl.net>
To: jackie.huang@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/6] nfs-utils: add init.d/nfsserver status command for LSB compliance
Date: Tue, 20 Aug 2013 07:36:01 +0100 [thread overview]
Message-ID: <1376980561.4083.25.camel@x121e.pbcl.net> (raw)
In-Reply-To: <13b92f067594e8aceac11c7964242fafdfb21f8d.1376968627.git.jackie.huang@windriver.com>
On Tue, 2013-08-20 at 11:25 +0800, jackie.huang@windriver.com wrote:
> @@ -23,6 +25,7 @@ test -r /etc/default/nfsd && . /etc/default/nfsd
> test -x "$NFS_MOUNTD" || NFS_MOUNTD=/usr/sbin/rpc.mountd
> test -x "$NFS_NFSD" || NFS_NFSD=/usr/sbin/rpc.nfsd
> test -x "$NFS_STATD" || NFS_STATD=/usr/sbin/rpc.statd
> +test -z "$STATD_PID" && STATD_PID=/var/run/rpc.statd.pid
> #
> # The user mode program must also exist (it just starts the kernel
> # threads using the kernel module code).
> @@ -75,6 +78,17 @@ stop_mountd(){
> #
> #nfsd
> start_nfsd(){
> + modprobe -q nfsd
> + grep -q nfsd /proc/filesystems || {
> + echo NFS daemon support not enabled in kernel
> + exit 1
> + }
> + grep -q nfsd /proc/mounts || mount -t nfsd nfsd /proc/fs/nfsd
> + grep -q nfsd /proc/mounts || {
> + echo nfsd filesystem could not be mounted at /proc/fs/nfsd
> + exit 1
> + }
> +
> echo -n "starting $1 nfsd kernel threads: "
> start-stop-daemon --start --exec "$NFS_NFSD" -- "$@"
> echo done
> @@ -113,14 +127,14 @@ stop_nfsd(){
> #statd
> start_statd(){
> echo -n "starting statd: "
> - start-stop-daemon --start --exec "$NFS_STATD"
> + start-stop-daemon --start --exec "$NFS_STATD" --pidfile "$STATD_PID"
> echo done
> }
> stop_statd(){
> # WARNING: this kills any process with the executable
> # name 'statd'.
> echo -n 'stopping statd: '
> - start-stop-daemon --stop --quiet --signal 1 --name statd
> + start-stop-daemon --stop --quiet --signal 1 --pidfile "$STATD_PID"
> echo done
> }
> #----------------------------------------------------------------------
This stuff doesn't seem to e directly related to the "status" command.
p.
next prev parent reply other threads:[~2013-08-20 6:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 3:25 [PATCH 0/6] Add status command for LSB compliance for some packages jackie.huang
2013-08-20 3:25 ` [PATCH 1/6] dbus: add init.d/dbus-1 status command for LSB compliance jackie.huang
2013-08-20 3:25 ` [PATCH 2/6] sysvinit: add init.d/bootlogd " jackie.huang
2013-08-20 6:39 ` Phil Blundell
2013-08-20 9:33 ` jhuang0
2013-08-20 3:25 ` [PATCH 3/6] nfs-utils: add init.d/nfsserver " jackie.huang
2013-08-20 6:36 ` Phil Blundell [this message]
2013-08-20 3:25 ` [PATCH 4/6] openssh: add init.d/sshd " jackie.huang
2013-08-22 6:42 ` Khem Raj
2013-08-22 7:02 ` jhuang0
2013-08-22 7:15 ` ChenQi
2013-08-20 3:25 ` [PATCH 5/6] sysklogd: add init.d/syslog " jackie.huang
2013-08-20 3:25 ` [PATCH 6/6] at: add init.d/atd " jackie.huang
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=1376980561.4083.25.camel@x121e.pbcl.net \
--to=pb@pbcl.net \
--cc=jackie.huang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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