On 15 Jul 2014, at 8:00 pm, Arjun Pandey <apandepub...@gmail.com> wrote:
> Right. Actually the issue i am facing is that i am starting the > pacemaker service remotely from a wrapper and thus pacemakerd dies > when the wrapper exits.nohup solves the problem but then HUP cannot be > used by pacemaker. Is this workaround ok ? I guess. How are you starting pacemaker? Usually its with some variant of 'service pacemaker start'. > > I was checking out the current pacemaker code.setsid is called for > each child process.However if we do this for main process to then it > will also be detached from the terminal. > > Regards > Arjun > > > > On Tue, Jul 15, 2014 at 3:01 PM, Andrew Beekhof <and...@beekhof.net> wrote: >> >> On 15 Jul 2014, at 7:13 pm, Arjun Pandey <apandepub...@gmail.com> wrote: >> >>> Hi Andrew >>> >>> AFAIK linux daemons don't terminate on SIGHUP. >> >> Read the man page, POSIX specifies that the default action is 'term' ie. >> 'terminate'. >> >>> They typically reload >>> configuration on receiving this signal.Eg- rsyslogd. I thought it was >>> safe to make this assumption here as well. >> >> Not anywhere as it turns out >> >>> >>> Regards >>> Arjun >>> >>> On Tue, Jul 15, 2014 at 2:15 PM, Andrew Beekhof <and...@beekhof.net> wrote: >>>> >>>> On 15 Jul 2014, at 6:19 pm, Arjun Pandey <apandepub...@gmail.com> wrote: >>>> >>>>> Hi all >>>>> >>>>> I am running pacemaker version 1.1.10-14.el6 on CentOS 6. On setting >>>>> up cluster if I send SIGHUP to either pacemaker or corosync services , >>>>> they die. >>>>> Is this a bug ? What is the intension behind this behavior? >>>> >>>> Standard default I believe. >>>> Have you run 'man 7 signal' lately? >>>> >>>> _______________________________________________ >>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>>> >>>> Project Home: http://www.clusterlabs.org >>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>>> Bugs: http://bugs.clusterlabs.org >>>> >>> >>> _______________________________________________ >>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>> >>> Project Home: http://www.clusterlabs.org >>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>> Bugs: http://bugs.clusterlabs.org >> >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
