From: Harald Dunkel <harald.dunkel@t-online.de>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: how to stop kernel nfsd?
Date: Wed, 10 Jun 2009 18:42:16 +0200 [thread overview]
Message-ID: <4A2FE268.60505@t-online.de> (raw)
In-Reply-To: <alpine.DEB.2.01.0906091907340.6439@bogon>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Christian Kujau wrote:
> On Mon, 8 Jun 2009, harald.dunkel@t-online.de wrote:
>> Which signal would be correct to gracefully kill the kernel nfs daemons?
>
> What are you trying to achieve? "killing", "terminating" or "graceful
> reloading", as in "re-exporting the shares", which can be done with
> exportfs(8).
>
Its a HA setup. Heartbeat is supposed to terminate the nfs service, umount
the local filesystem, set the drbd resources to "secondary", and release
the shared IP address (in this sequence).
To terminate the nfs service Lenny's /etc/init.d/nfs-kernel-server tries
kill -INT <pid>
for all nfs daemons. Even though nfs is not active the nfs daemons don't
go away and keep the local mount point busy. If I patch the nfs runlevel
script to use SIGQUIT or SIGHUP instead, then the nfs daemons terminate.
Lenny's kernel is 2.6.26 plus patches.
Surely I am not asking for support for Lenny's kernel. But it would be
interesting to know what the kernel nfs daemons are supposed to do when
they receive a signal. AFAICS this is not documented.
Regards
Harri
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2009-06-10 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 10:52 how to stop kernel nfsd? harald.dunkel
2009-06-10 2:13 ` Christian Kujau
2009-06-10 16:42 ` Harald Dunkel [this message]
2009-06-10 19:25 ` Christian Kujau
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=4A2FE268.60505@t-online.de \
--to=harald.dunkel@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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