John Goerzen wrote:
Christopher Phillips (Blake) wrote:
I sent in the same patches for bacula-sd and bacula-director. Since,
those are daemons that should not be running on all hosts, they make
more sense to enable/disable, especially if you're using a generated
image across many hosts.
The bacula-fd version was to be consistent. If you don't have the
/etc/default/bacula-fd file in place, the init script still works.
I am still really not sure this is sensible. Isn't this what
update-rc.d is supposed to do?
In our environment, we use systemimager to create a base image for all
hosts. It's much easier for us to have everything enabled in
/etc/runlevel.conf and then disable/enable a daemon using
/etc/default/$FOO and have that file revision controlled rather than
editing each machines' /etc/runlevel.conf. Also, adding the
/etc/default/$FOO file allows us to modify the behavior of the script in
other ways. I only make this suggestion as other systems administrators
may find the same. Section 9.3.2 of the Debian Policy Manual includes
this as well.
Some other packages that enable/disable using /etc/default:
icecast2
spamassassin
rsync
bootlogd
sysstat
monit
fetchmail
firehol
Thank you,
Chris.
