2010/9/3 Fabio M. Di Nitto <fabbi...@fabbione.net>: > so the current init script has: > >> # chkconfig: - 20 20 > > and that is definitely wrong. It must have slept through the crack when > we re-did the init script a while ago. Kudos to Vladislav for noticing it. > > (making a bunch of assumptions here) the general rule is: > > stop-priority-value = 100 - start-priority-value. > > to guarantee the service start/stop symmetry that is pretty much the > case for corosync. > > So a value of 20/80 would be correct. > > Now this should address the first concern reported.
As for the starting order, I would be grad if you could also consider the attached patch. It will adjust the dependency with syslog correctly so that can prevent a problem when you use rsyslog as I reported before: https://lists.linux-foundation.org/pipermail/openais/2010-July/014946.html Thanks, -- Keisuke MORI
--- corosync-1.2.8/init/generic.in.orig 2010-09-03 16:42:39.000000000 +0900 +++ corosync-1.2.8/init/generic.in 2010-09-03 16:46:34.000000000 +0900 @@ -12,9 +12,8 @@ # ### BEGIN INIT INFO # Provides: corosync -# Required-Start: $network -# Should-Start: $syslog -# Required-Stop: $network +# Required-Start: $network $syslog +# Required-Stop: $network $syslog # Default-Start: # Default-Stop: # Short-Description: Starts and stops Corosync Cluster Engine.
_______________________________________________ Openais mailing list Openais@lists.linux-foundation.org https://lists.linux-foundation.org/mailman/listinfo/openais
