On Friday 09 February 2007 12:34, Alan Brown wrote:
> On Fri, 9 Feb 2007, Kern Sibbald wrote:
> > Just so that it is clear, Eric did propose this change to me before
> > implementing it, and I agreed, but clearly I was wrong and did not
> > understand all the consequences. Anyway, I hope we can fi
On Fri, 9 Feb 2007, Kern Sibbald wrote:
> Just so that it is clear, Eric did propose this change to me before
> implementing it, and I agreed, but clearly I was wrong and did not
> understand all the consequences. Anyway, I hope we can fix it.
If the early disconnect feature is implenented, th
Hello,
Just so that it is clear, Eric did propose this change to me before
implementing it, and I agreed, but clearly I was wrong and did not understand
all the consequences. Anyway, I hope we can fix it.
Regards,
Kern
On Friday 09 February 2007 11:09, Andrea Conti wrote:
> > Yes, the Direct
> Yes, the Director conf file is by far the most difficult to setup. The only
> good point is that I heard a number of times that it is easier than most
> other software.
I was not complaining by any means: a bit of complexity is a good price
for the great flexibility you get. And the most diff
Hello,
On Thursday 08 February 2007 20:21, Andrea Conti wrote:
> Hello,
>
> I have been using bacula for more than a year to back up a small number
> of machines. I am perfectly happy with the software, despite a certain
> initial difficulty in setting up a working configuration.
Yes, the Directo
On Friday 09 February 2007 05:21, Eric Bollengier wrote:
> Hi,
>
> > > > When I recently upgraded to 2.0 I found out the hard way that the
> > > > RunClientAfterJob directive semantics changed quite a bit with the
> > > > new version: while in 1.38 the script was run after all activities
> > > > re
Hi,
> > > When I recently upgraded to 2.0 I found out the hard way that the
> > > RunClientAfterJob directive semantics changed quite a bit with the new
> > > version: while in 1.38 the script was run after all activities
> > > requiring a connection with the client were over (including data and
>
On Thursday 08 February 2007 21:57, Eric Bollengier wrote:
> Hello,
>
> > When I recently upgraded to 2.0 I found out the hard way that the
> > RunClientAfterJob directive semantics changed quite a bit with the new
> > version: while in 1.38 the script was run after all activities requiring
> > a c
> If you want send your command at the real end of backup, you can use
> RunAfterJob with some ssh or smb command. (for windows see Samba-TNG
> http://lists.samba.org/archive/samba/2000-April/018388.html)
I'll look into that (even if it looks like a workaround more than a
solution ;).
Thanks for
