Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

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

    pfSense Packages
    2
    5
    1426
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      Reiner030 last edited by

      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"}
      
      
      1 Reply Last reply Reply Quote 0
      • marcelloc
        marcelloc last edited by

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

        Treinamentos de Elite: http://sys-squad.com

        Help a community developer! ;D

        1 Reply Last reply Reply Quote 0
        • R
          Reiner030 last edited by

          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):(

          1 Reply Last reply Reply Quote 0
          • marcelloc
            marcelloc last edited by

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

            Treinamentos de Elite: http://sys-squad.com

            Help a community developer! ;D

            1 Reply Last reply Reply Quote 0
            • R
              Reiner030 last edited by

              @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).

              1 Reply Last reply Reply Quote 0
              • First post
                Last post