Package: quagga
Version: 0.98.3-7.2
Severity: minor
We're using quagga with heartbeat and ldirectord to propagate routes to
virtual IPs.
This means quagga must be installed on all the nodes in the cluster but
will be started under heartbeat control by a specific startup script
(different from the one provided in the package).
We need a way to ensure that quagga won't be automatically restarted
when the server is started or the package updated.
I provide a patch based on the ssh initscript that allow such control by
creating a file named /etc/quagga/quagga_not_to_be_run, but there's
obviously more than one way to do it.
Cheers,
Gildas
--- quagga.orig 2005-05-06 12:51:21.000000000 +0100
+++ quagga 2007-02-26 10:58:05.949948165 +0000
@@ -11,6 +11,14 @@
C_PATH=/etc/quagga
DAEMONS="zebra bgpd ripd ripngd ospfd ospf6d" # keep zebra first!
+check_for_no_start() {
+ # forget it if we're trying to start, and
/etc/quagga/quagga_not_to_be_run exists
+ if [ -e /etc/quagga/quagga_not_to_be_run ]; then
+ echo "Quagga daemons $DAEMONS not in use
(/etc/quagga/quagga_not_to_be_run)"
+ exit 0
+ fi
+}
+
# Print the name of the pidfile.
pidfile()
{
@@ -66,6 +74,8 @@
echo -n " $1"
if ! check_daemon $1; then return; fi
+ check_for_no_start
+
start-stop-daemon \
--start \
--pidfile=`pidfile $1` \