From: Gabriel Barazer <gabriel@oxeva.fr>
To: nfs@lists.sourceforge.net
Subject: the right way to stop NFS
Date: Thu, 19 Jul 2007 17:32:38 +0200 [thread overview]
Message-ID: <469F8416.5010309@oxeva.fr> (raw)
Hi,
In the readme file, there is the detailed startup order for the NFS
server and client subsystem, which is very useful especially for
maintainers. But there isn't any description for stopping NFS services.
On the client, the stop order is almost obvious : unmount nfs
filesystems, kill statd, kill idmapd and gssd and you are done. But what
is the right stop order for a server ?
We have :
- svcgssd
- idmapd
- rpc.statd
- nfsd kernel daemons
- mountd
I don't know if we have to stop nfsd first (rpc.nfsd 0) , or maybe
rpc.mountd ? or even unexport fs first ?
Is there any NFS guru to point this out ?
Thanks,
Gabriel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2007-07-19 15:32 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=469F8416.5010309@oxeva.fr \
--to=gabriel@oxeva.fr \
--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