supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: TheOldFellow <theoldfellow@gmail.com>
Subject: Re: rpc.nfsd, rpc.mountd
Date: Tue, 17 May 2005 13:54:41 +0100	[thread overview]
Message-ID: <4289E991.3040608@gmail.com> (raw)
In-Reply-To: <20050517122528.16814.qmail@93361de9ea22df.315fe32.mid.smarden.org>

Gerrit Pape wrote:
> On Fri, May 06, 2005 at 03:43:26PM +0100, Richard A Downing FBCS CITP wrote:
> 
>>H.M. Dijkstra wrote:

> 
> Hi, looks like the mountd run script on the web page isn't accurate, it
> should 'exec' into rpc.mountd, e.g.:
> 
>  #!/bin/sh
>  exec 2>&1
>  RPCNFSDCOUNT=8  # Number of servers to be started up by default
>  RPCMOUNTDOPTS=-F
>  exportfs -r
>  rpc.nfsd -- $RPCNFSDCOUNT
>  rpcinfo -u localhost nfs 3 >/dev/null 2>&1 || \
>    RPCMOUNTDOPTS="$RPCMOUNTDOPTS --no-nfs-version 3"
>  exec rpc.mountd $RPCMOUNTDOPTS
> 
> Stopping the service will still leave the nfsd (and lockd) threads
> running though.  I don't like the pid-guessing applications like pidof
> or start-stop-daemon, a `rpc.nfsd -- 0` in ./finish maybe can help here.
> 
> HTH, Gerrit.
> 
Gerrit,
I'd reached the same conclusions. There are my new scripts for LFS-6.

run:
------------------------
#!/bin/bash
exec 2>&1
# Make sure the statd service is running.
# (the statd service should ensure portmap is running first)
svwaitup /var/service/statd
# Get the nfs service parameters from the LFS standard file
# this sets some envars.
source /etc/sysconfig/nfs-server
# Re-export all directories in /etc/exports
/sbin/exportfs -ra > /dev/null
# start some nfsd threads
/sbin/rpc.nfsd -- $PROCESSES
# Start the rpc.mountd daemon
exec /sbin/rpc.mountd --foreground
------------------------

finish:
------------------------
#!/bin/sh
exec 2>&1
# shut down the nfsd threads.
rpc.nfsd -- 0
------------------------

R.


      reply	other threads:[~2005-05-17 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-19 14:02 H.M. Dijkstra
2005-05-06 14:43 ` Richard A Downing FBCS CITP
2005-05-17 12:25   ` Gerrit Pape
2005-05-17 12:54     ` TheOldFellow [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=4289E991.3040608@gmail.com \
    --to=theoldfellow@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;
as well as URLs for NNTP newsgroup(s).