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
Package: bacula-director-common
Severity: Normal
Version: 2.4.4-1
Tags: patch
Change to /etc/init.d/bacula-director to use
/etc/default/bacula-director to enable/disable the daemon.
--- bacula-director 2009-05-22 14:33:38.0 -0700
+++ /etc/init.d/bacula-director 2009-03-18 17:27:01.
x27;t have the
/etc/default/bacula-fd file in place, the init script still works.
Chris.
John Goerzen wrote:
What is the point of installing bacula-fd and then not running it?
That just doesn't make sense to me.
Christopher Phillips (Blake) wrote:
Package: bacula-fd
Severity: Normal
Package: bacula-sd
Severity: Normal
Version: 2.4.4-1
Tags: patch
Change to /etc/init.d/bacula-sd to use /etc/default/bacula-sd to
enable/disable the daemon.
--- bacula-sd 2009-05-22 14:23:33.0 -0700
+++ /etc/init.d/bacula-sd 2009-03-31 04:48:13.0 -0700
@@ -38,6 +38,12 @
Package: bacula-fd
Severity: Normal
Version: 2.4.4-1
Tags: patch
I believe that bacula-fd should be enabled or disabled using the
/etc/default/bacula-fd file. I'm submitting a patch to
/etc/init.d/bacula-fd to include this.
--- bacula-fd2009-05-22 13:31:25.0 -0700
+++ /etc/init.d/
5 matches
Mail list logo