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 05:44:32 +0200 [thread overview]
Message-ID: <4FDFF5A0.3050302@redhat.com> (raw)
In-Reply-To: <20120614160650.GA843695@redhat.com>
On 06/14/2012 06:06 PM, Ryan McCabe wrote:
> On Thu, Jun 14, 2012 at 03:41:39PM +0000, Dietmar Maurer wrote:
>> I can't see that in the current cman init script. Instead, the rgmanager
>> init script depends on the cpglockd unconditionally:
>>
>> # Required-Start: cman cpglockd
>>
>> So that is a bug?
>
> Hi,
>
> 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.
The Required-Start: tells sysvinint that if cpglockd is enabled, it has
to be started before rgmanager.
rgmanager snippet to start cpglockd is there only for backward
compatibility mode that avoids breaking upgrades from non RRP
environments to RRP. This was done so that users didn't need to enable
cpglockd via chkconfig (being a new daemon and all is not known yet).
A "perfect" install would see the user doing:
chkconfig cpglockd on
chkconfig rgmanager on
only for RRP installations. But then again, docs are fresh, cpglockd is
new.. might as well help the users not to shoot their foot with an RRP
gun ;)
Fabio
next prev parent reply other threads:[~2012-06-19 3:44 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 [this message]
2012-06-19 4:23 ` Dietmar Maurer
2012-06-19 6:20 ` Fabio M. Di Nitto
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=4FDFF5A0.3050302@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 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).