On Saturday 18 October 2008 15:30:46 T. Horsnell wrote:
> >>>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.

I would say it is easy to deal with this, I think : 

  RunBeforeJob = "echo \"disable job=Job1\" | /usr/bacula/bin/bconsole"
  RunAfterJob = "echo \"enable Job1\" | /usr/bacula/bin/bconsole"
  RunAfterFailedJob  = "echo \"enable job=Job1\" | /usr/bacula/bin/bconsole"

This in your job should do. I'm just waiting till tomorrow to check if it's 
working fine.

-- 
Piotr Gbyliczek
Second Line Support 
Forlinux LTD

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


-------------------------------------------------------------------------
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