On Thu, 16 Oct 2008, Arno Lehmann 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
>
> Now this is a really slick way to solve that (works only with 2.erm...
> don't know now though, because job enabling/disabling wasn't always
> available).

I wonder if there's a more general way of doing this than having 1
RunBefore/RunAfter per job.

AB


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