On Monday 05 March 2007 16:12, Ryan Novosielski wrote:
> Kern Sibbald wrote:
> > On Monday 05 March 2007 07:47, Ryan Novosielski wrote:
> >> Tim Schaab wrote:
> >>> Howdy,
> >>>
> >>> What could be preventing a FD from sending the OK status to the
> >>> Director after a backup?
> >>
> >> I don't kn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kern Sibbald wrote:
> On Monday 05 March 2007 07:47, Ryan Novosielski wrote:
>> Tim Schaab wrote:
>>> Howdy,
>>>
>>> What could be preventing a FD from sending the OK status to the Director
>>> after a backup?
>> I don't know how important this is, but
On Monday 05 March 2007 07:47, Ryan Novosielski wrote:
> Tim Schaab wrote:
> > Howdy,
> >
> > What could be preventing a FD from sending the OK status to the Director
> > after a backup?
>
> I don't know how important this is, but I often almost forget to change
> the "Messages" resource at the bot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Schaab wrote:
> Howdy,
>
> What could be preventing a FD from sending the OK status to the Director
> after a backup?
I don't know how important this is, but I often almost forget to change
the "Messages" resource at the bottom of the -fd config
Tim Schaab skrev:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Howdy,
>
> What could be preventing a FD from sending the OK status to the Director
> after a backup?
>
> I am working on rolling out Bacula to the department here. The roll out
> has been smooth with the exception of two co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Howdy,
What could be preventing a FD from sending the OK status to the Director
after a backup?
I am working on rolling out Bacula to the department here. The roll out
has been smooth with the exception of two computers that are behind a
firewall.
W
