John Drescher wrote:
> On Fri, Oct 17, 2008 at 5:54 AM, Piotr Gbyliczek <pg AT forlinux.co DOT uk> 
> wrote:
> 
>>On Thursday 16 October 2008 17:40:16 T. Horsnell wrote:
>>
>>
>>>I had this problem from the start. I ended up with a line in my
>>>RunBefore script which disabled the backup job:
>>>
>>>   echo "disable job=Job1" | /usr/local/bacula/bin/bconsole
>>>
>>>This disables any further scheduling of Job1 but leaves the current one
>>>running.
>>>
>>>And in the RunAfter script I have
>>>   echo "run job=BackupCatalog yes" | /usr/local/bacula/bin/bconsole
>>>   echo "enable job=Job1" | /usr/local/bacula/bin/bconsole
>>
>>
>>That is really, really clever trick. Thanks for tip, Terry.
>>
> 
> My only question is if the job fails for some reason doesn't that
> leave it disabled because the Run After script does not get executed?

Yes, this is a risk. I dont know whether the RunAfter script gets run if 
the actual backup itself fails - it hasnt happened yet, but its 
something to be aware of.

Cheers,
Terry

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users