[Pacemaker] chkconfig values in MCP init script (again)

[Vladislav Bogdanov]

22.09.2010 11:17, Andrew Beekhof wrote:
> On Tue, Sep 21, 2010 at 2:24 PM, Vladislav Bogdanov
> <bubble at hoster-ok.com> wrote:
>> Hi Andrew, hi all.
>>
>> I decided to return to this issue again because of issues with
>> libvirt/KVM virtual domains controlled by pacemaker.
>>
>> libvirt package on Fedora 13 has two init scripts: libvirtd and
>> libvirt-guests.
>> They have following chkconfig values:
>> libvirtd: 97 03
>> libvirt-guests: 98 02
>>
>> Currently pacemaker MCP has 90 10.
>>
> 
> ...
> 
>> So, the next solution would be to move pacemaker to run really last (99)
>> and stop really first (01). This is what Vadim Chepkov suggested earlier
>> and what I am inclined to do (at least for my RPM packages). Of course,
>> there are services which have 99 01 too, but I'd shut eyes on them.
> 
> I'm fine with that.  I'll make the change now.
> Possibly some stop-requires might be of use too.

I'd add corosync to Required-Stop.

Adding other services like libvirtd is not an option I think. You cannot
predict what resources are actually run by pacemaker, so you cannot
enumerate them all.