From: Fabio M. Di Nitto <fdinitto@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] when do I need to start cpglockd
Date: Tue, 19 Jun 2012 08:20:33 +0200 [thread overview]
Message-ID: <4FE01A31.7080506@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F754B95DC60@lisa.maurer-it.com>
On 6/19/2012 6:23 AM, Dietmar Maurer wrote:
>>> Yes, that's a bug. cpglockd will be started from the rgmanager init
>>> script when RRP mode is enabled.
>>>
>>>
>>> Ryan
>>>
>>
>> Actually no, it's not a bug.
>>
>> cpglockd has it's own init script too.
>
> Yes, and that script 'unconditionally' (always) starts cpglockd
Nothing wrong with that. If you ask a daemon to start it will start :)
On top of that, cpglockd is harmless if there is no RRP mode active, or
forcefully disabled.
>
>> The Required-Start: tells sysvinint that if cpglockd is enabled, it has to be
>> started before rgmanager.
>
> That tells sysvinint to always start that script before rgmanager.
>
> So we end up with cpglockd always running, although it is not required at all.
>
> What do I miss?
It tells sysvinit to start cpglockd before rgmanager IF cpglockd is
enabled via chkconfig, otherwise it is not started. That value is used
only to calculate the symlink S* K** values for rc.d/
Fabio
next prev parent reply other threads:[~2012-06-19 6:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 15:26 [Cluster-devel] when do I need to start cpglockd Dietmar Maurer
2012-06-14 12:21 ` Ryan McCabe
2012-06-14 15:41 ` Dietmar Maurer
2012-06-14 16:06 ` Ryan McCabe
2012-06-19 3:44 ` Fabio M. Di Nitto
2012-06-19 4:23 ` Dietmar Maurer
2012-06-19 6:20 ` Fabio M. Di Nitto [this message]
2012-06-19 6:54 ` Dietmar Maurer
2012-06-19 7:03 ` Fabio M. Di Nitto
2012-06-19 7:24 ` Dietmar Maurer
2012-06-19 8:04 ` Fabio M. Di Nitto
2012-06-19 8:12 ` Dietmar Maurer
2012-06-19 8:33 ` Fabio M. Di Nitto
2012-06-19 8:36 ` Dietmar Maurer
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=4FE01A31.7080506@redhat.com \
--to=fdinitto@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.