Alan,
> Spool Directory /bacula/working
If you entered the Spool Directory directive as you specified it in your
email, then it is probably malformed. I believe the proper format is:
Spool Directory *=* /bacula/working
You will need to restart bacula-sd after adding the new directive to
bacula-s
Bill:
Thanks for getting back so quickly. In my original (non spool file
inclusion) i get:
tcp 0 0 0.0.0.0:9103 0.0.0.0:* LISTEN 10177/bacula-sd
Including the spool file directive I get nothing. In all conf files I
list the host name as slcakware.polinsky.home
In Slac
On 5/29/25 3:02 PM, Alan Polinsky wrote:
I've been running Bacula 9.6.7 for many years with an attached LTO3 tape drive. The machine hosting Bacula is an old Dell
Optiplex. Though I am always in Slackware, there is a small 250 gig drive that had Windows 10 installed on it, even though It
was nev
I've been running Bacula 9.6.7 for many years with an attached LTO3 tape
drive. The machine hosting Bacula is an old Dell Optiplex. Though I am
always in Slackware, there is a small 250 gig drive that had Windows 10
installed on it, even though It was never booted in that operating
system. With
Thank you to Jonathan, David, and Martin for their helpful replies. They
helped me find a solution that worked for me.
*A question, upfront: Is there any documentation on wild directives, and
the rules around how they pattern match? The information I found in the
manual was vague or at times incor
