On 6/7/2010 4:24 PM, Vadym Chepkov wrote: > On Mon, Jun 7, 2010 at 9:03 AM, Fabio M. Di Nitto <[email protected]> wrote: >> On 6/7/2010 2:56 PM, Vadym Chepkov wrote: >> >>> It would be nice to prevent this from happening though: >>> >>> ls /etc/rc3.d/*corosync* >>> /etc/rc3.d/S99corosync >>> >>> yum -y update >>> Updating: >>> corosync x86_64 1.2.2-1.1.el5 >>> clusterlabs 148 k >>> corosynclib x86_64 1.2.2-1.1.el5 >>> clusterlabs 170 k >>> >>> # ls /etc/rc3.d/*corosync* >>> /etc/rc3.d/S20corosync >>> >>> Is it corosync's rpm fault? Why priorities getting reset? >> >> The init script gets replaced with the new one (with original values) on >> updates and chkconfig is executed. That recalculates the whole position >> of the init script with the new values. >> >> I think that愀 just the way rpm works in general as the init script is >> not considered a user modifiable config file. >> >> Fabio >> > > I could be wrong, but wouldn't this cure it ? > > %post > if [ "$1" = 1 ] > then > /sbin/chkconfig --add corosync > fi
IIRC it would isolate the call to chkconfig, but the custom values you set in the init script, would still be overwritten by the update. So it would act as temporary workaround, but won´t solve your specific problem completely. Fabio _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
