On Sep 2, 2010, at 5:04 PM, Steven Dake wrote:
> On 09/02/2010 01:28 PM, Vadym Chepkov wrote:
>>
>> On Sep 2, 2010, at 3:09 PM, Steven Dake wrote:
>>
>>> On 08/31/2010 08:45 PM, Vladislav Bogdanov wrote:
>>>> Hi,
>>>> 31.08.2010 22:22, Steven Dake wrote:
>>>>> I am pleased to announce Corosync 1.2.8 is available for immediate
>>>>> download from our website.
>>>>
>>>> Initscript doesn't seem to be fixed yet.
>>>> http://marc.info/?l=openais&m=128271460429681&w=2
>>>> http://www.mail-archive.com/pacema...@oss.clusterlabs.org/msg05833.html
>>>>
>>>> Best,
>>>> Vladislav
>>>
>>> Fabio,
>>>
>>> Any chance you can provide feedback on this topic? I'm at a loss in
>>> this area of distro integration.
>>>
>>
>> I have complained about it some time ago, but was dismissed :)
>
> Vadym,
>
> My general take is it is the responsibility of individual distros to tailor
> the init scripts to their particular startup order.
>
> But rather then you being dismissed, I'd like to hear Fabio's reasoning so we
> can all come to some agreement. Unfortunately I don't know enough about the
> particulars of the init script dependencies to make that judgement. Fabio
> should be able to provide appropriate reasoning.
>
> Regards
> -steve
>
>> So, I build my own rpm
>>
>> diff -ur corosync-1.2.4.orig/init/generic.in corosync-1.2.4/init/generic.in
>> --- corosync-1.2.4.orig/init/generic.in 2010-03-22 12:08:57.000000000
>> -0400
>> +++ corosync-1.2.4/init/generic.in 2010-07-28 10:00:00.000000000 -0400
>> @@ -6,7 +6,7 @@
>> #
>> # License: Revised BSD
>>
>> -# chkconfig: - 20 20
>> +# chkconfig: - 99 01
>> # description: Corosync Cluster Engine
>> # processname: corosync
>> #
>>
>>
>
This is one of those cases where you can't make everybody happy. In some cases
corosync needs to start early to support cman/gfs, in other case it needs to
start later to support XEN with drbd block device. so 20 vs 99 is pretty much
subjective and since you added
postinstall scriptlet (using /bin/sh):
if [ $1 -eq 1 ]; then
/sbin/chkconfig --add corosync || :
fi
it doesn't destroy local preferences during upgrade, so it is just something
that administrator has to decide for himself.
I need to have corosync to start after ntpd, after sendmail, after winbind,
after xend and this pretty much leaves me with 99
Vadym
_______________________________________________
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/openais
