Christian Hammers wrote:
Hello
On 2007-02-26 Gildas Le Nadan wrote:
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.
I would prefer if this is handled by the typical invoke-rc.d mechanisms instead
of a package specific config file.
Take a look at "man invoke-rc.d" which is used by quagga and maybe at the
policyrcd-script-zg2 package and
your /etc/runlevel.conf.
I guess that removing quagga from runlevel.conf (or /etc/rcX.d/) will tell
invoke-rc.d not to start quagga.
bye,
-christian-
Hi Christian,
I'm not sure I follow, as if I understand correctly your solution with
/etc/runlevel.conf adds a dependency on the package file-rc. This is not
ideal as it is quite a major change: we have plenty of machines here and
people expect the usual symlink system to be in place.
You seem to imply by citing invoke-rc.d that using "update-rc.d -f
quagga remove" to remove the links in /etc/rc*d will just work, but it
doesn't afaik: the links are automagically re-created when the package
is updated and the daemons are started.
This is why I offered a method similar to the one used by sshd. It seems
less intrusive for me (no external dependencies), may be put in place
only for the ones who needs it and even reminds you that it is there by
displaying a message on start-up.
You might consider changing the severity to whishlist.
Cheers,
Gildas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
