Hello,

I cannot say what happens on FreeBSD, but the paths are definitely not
hardcoded.  They are set during the ./configure process.  So, either there
is some bug with FreeBSD or the ./configure line you used is incorrect.

Any change to delete_catalog_backup will simply be overwritten the next
time a ./configure is done since it is generated each time from delete_catalog_backup.in

Regards,

Kern

On 09/30/2011 07:57 AM, Eimar Koort wrote:
Hi,

Problem is that catalog backup paths are hardcoded and scripts are
failing if 'working dir' is not /var/db/bacula:

Director {
WorkingDirectory = "/data/bacula"

Original files are located in /usr/local/share/bacula/ directory on FreeBSD.

I also added two small patches. I'm aware that one of those patches is
specific to FreeBSD. However - they should just give idea.

Regards,
--
Eimar Koort
( eimar.ko...@gmail.com )


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2


_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to