cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: rohara@sourceware.org <rohara@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/ccs/daemon ccsd.c
Date: 31 Aug 2006 17:49:17 -0000	[thread overview]
Message-ID: <20060831174917.893.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	cluster
Changes by:	rohara at sourceware.org	2006-08-31 17:49:16

Modified files:
	ccs/daemon     : ccsd.c 

Log message:
	Moved code which signals parent (SIGTERM), which allows the parent process
	to continue and exit. This signal was occuring before ccsd had the sockets
	ready for communication, and as a result the cman init script would sometimes
	fail because the ccsd would daemonize before the socket was ready.
	
	This fix will not signal the parent until ccsd is ready (socket is created
	and ready; before select() loop).

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/ccs/daemon/ccsd.c.diff?cvsroot=cluster&r1=1.25&r2=1.26

--- cluster/ccs/daemon/ccsd.c	2006/08/30 17:35:40	1.25
+++ cluster/ccs/daemon/ccsd.c	2006/08/31 17:49:16	1.26
@@ -181,6 +181,9 @@
   if (sfds[2] >= 0) 
     FD_SET(sfds[2], &rset);
 
+  log_dbg("Sending SIGTERM to parent\n");
+  kill(getppid(), SIGTERM);
+
   while(1){
     unsigned int len = addr_size;
 
@@ -755,7 +758,7 @@
     }
 
     /* Make the parent stop waiting */
-    kill(getppid(), SIGTERM);
+    /* kill(getppid(), SIGTERM); */
   }
 
   signal(SIGINT, &sig_handler);



             reply	other threads:[~2006-08-31 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-31 17:49 rohara [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-30 21:31 [Cluster-devel] cluster/ccs/daemon ccsd.c rmccabe
2006-08-30 17:35 rohara
2006-08-16 14:49 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=20060831174917.893.qmail@sourceware.org \
    --to=rohara@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).