From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/group/dlm_controld dlm_daemon.h main.c
Date: 9 Feb 2007 16:05:30 -0000 [thread overview]
Message-ID: <20070209160530.28747.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: teigland at sourceware.org 2007-02-09 16:05:30
Modified files:
group/dlm_controld: dlm_daemon.h main.c
Log message:
clear configfs stuff if we get SIGTERM, this is a convenience if you
want to kill dlm_controld and remove the dlm module without leaving
the cluster. Otherwise you have to manually clear configfs dirs.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/dlm_controld/dlm_daemon.h.diff?cvsroot=cluster&r1=1.6&r2=1.7
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/dlm_controld/main.c.diff?cvsroot=cluster&r1=1.8&r2=1.9
--- cluster/group/dlm_controld/dlm_daemon.h 2007/01/09 19:17:08 1.6
+++ cluster/group/dlm_controld/dlm_daemon.h 2007/02/09 16:05:30 1.7
@@ -39,6 +39,7 @@
#include <time.h>
#include <syslog.h>
#include <sched.h>
+#include <signal.h>
#include <linux/netlink.h>
#include "list.h"
--- cluster/group/dlm_controld/main.c 2007/01/09 19:17:08 1.8
+++ cluster/group/dlm_controld/main.c 2007/02/09 16:05:30 1.9
@@ -23,6 +23,11 @@
extern group_handle_t gh;
+static void sigterm_handler(int sig)
+{
+ if (list_empty(&lockspaces))
+ clear_configfs();
+}
struct lockspace *create_ls(char *name)
{
@@ -423,6 +428,8 @@
if (!daemon_debug_opt)
daemonize();
+ signal(SIGTERM, sigterm_handler);
+
set_scheduler();
return loop();
next reply other threads:[~2007-02-09 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 16:05 teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-09 16:05 [Cluster-devel] cluster/group/dlm_controld dlm_daemon.h main.c teigland
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=20070209160530.28747.qmail@sourceware.org \
--to=teigland@sourceware.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;
as well as URLs for NNTP newsgroup(s).