[Pacemaker] Signal hangup handling for pacemaker and corosync

[Andrew Beekhof]

On 15 Jul 2014, at 7:13 pm, Arjun Pandey <apandepublic at 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 <andrew at beekhof.net> wrote:
>> 
>> On 15 Jul 2014, at 6:19 pm, Arjun Pandey <apandepublic at 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 at 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 at 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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140715/906511d4/attachment-0004.sig>