BUG: bacula-fd.sh service starter tries wrong config path (fix)

[Reiner030]

Hi,

this problem exists some versions… wondering how package maintainer and other people handle it without this fix ;)

--- /usr/local/etc/rc.d/bacula-fd.sh.orig	2013-02-27 20:34:51.000000000 +0100
+++ /usr/local/etc/rc.d/bacula-fd.sh	2013-02-27 20:55:25.000000000 +0100
@@ -24,5 +24,5 @@

 : ${bacula_fd_enable="YES"}
-: ${bacula_fd_flags=" -u root -g wheel -v -c /usr/pbi/bacula-amd64/etc/bacula-fd.conf"}
+: ${bacula_fd_flags=" -u root -g wheel -v -c /usr/local/etc/bacula-fd.conf"}
 : ${bacula_fd_pidfile="/var/run/bacula-fd.9102.pid"}

[marcelloc]

This fix force pfsense2.1, I'll ping package maintainer to include pfsense version check.

[Reiner030]

ping… its boring to take care after each reboot/several times when bacula crashes without unknown causes to reapply the patch every time again and again (auto-apply pitily didn't help/work here):(

[marcelloc]

I've pushed a fix for this, upadate to latest package version and test again.

[Reiner030]

@marcelloc:

I've pushed a fix for this, upadate to latest package version and test again.

thank you… works on both version now as expected ;)

(Problem was the the patch must applied every reboot/"crash" situation and not only once after install).