[Cluster-devel] when do I need to start cpglockd

[Dietmar Maurer]

> -----Original Message-----
> From: Ryan McCabe [mailto:rmccabe at redhat.com]
> Sent: Donnerstag, 14. Juni 2012 14:21
> To: Dietmar Maurer
> Cc: cluster-devel at redhat.com
> Subject: Re: [Cluster-devel] when do I need to start cpglockd
> 
> On Wed, Jun 13, 2012 at 03:26:22PM +0000, Dietmar Maurer wrote:
> > I just tried to upgrade my packages form STABEL31 to STABLE32, and
> noticed that there is a new daemon 'cpglockd'
> >
> > That daemon is always started with the default init script. Is that really
> necessary?
> >
> > I just wonder why rgmanager needs 2 different locking mechanism - dlm
> and cpglockd?
> [snip]
> > But why do I want to enable CPG-based locking, or why not?
> 
> Cpglockd was created to work around problems (mainly very slow failover)
> when corosync's RRP mode is enabled and dlm locking is used. It will be
> started from the cman init script only when RRP mode is detected. In this
> case, dlm locks won't be used at all by rgmanager.

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?

- Dietmar