02.09.2010 23:28, 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 :) > So, I build my own rpm
I have to do this too. > > 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 > # > > BTW 99 01 is too late start for pacemaker MCP (ver 1) which should be started later and stopped earlier. Now it has 90 10. And with MCP personally I do not see anything against starting corosync/openais early enough (just after network up). For judgment: Here is relevant part from Fedora's /etc/rc ========== # First, run the KILL scripts. for i in /etc/rc$runlevel.d/K* ; do # Check if the subsystem is already up. subsys=${i#/etc/rc$runlevel.d/K??} [ -f /var/lock/subsys/$subsys ] || [ -f /var/lock/subsys/$subsys.init ] || continue check_runlevel "$i" || continue # Bring the subsystem down. [ -n "$UPSTART" ] && initctl emit --quiet stopping JOB=$subsys $i stop [ -n "$UPSTART" ] && initctl emit --quiet stopped JOB=$subsys done # Now run the START scripts. for i in /etc/rc$runlevel.d/S* ; do # Check if the subsystem is already up. subsys=${i#/etc/rc$runlevel.d/S??} [ -f /var/lock/subsys/$subsys ] && continue [ -f /var/lock/subsys/$subsys.init ] && continue check_runlevel "$i" || continue # If we're in confirmation mode, get user confirmation if [ "$do_confirm" = "yes" ]; then confirm $subsys rc=$? if [ "$rc" = "1" ]; then continue elif [ "$rc" = "2" ]; then do_confirm="no" fi fi update_boot_stage "$subsys" # Bring the subsystem up. [ -n "$UPSTART" ] && initctl emit --quiet starting JOB=$subsys if [ "$subsys" = "halt" -o "$subsys" = "reboot" ]; then export LC_ALL=C exec $i start fi $i start [ -n "$UPSTART" ] && initctl emit --quiet started JOB=$subsys done ========= Bash (and shell in general) wildcards are resolved in natural (ASCII in our case) sorted order. man bash: ========= Pathname Expansion After word splitting, unless the -f option has been set, bash scans each word for the characters *, ?, and [. If one of these characters appears, then the word is regarded as a pattern, and replaced with an alphabeti- cally sorted list of file names matching the pattern. ========= Hope this clarifies how Fedora/EL do start/stop sequence. Best, Vladislav _______________________________________________ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais