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

You could put

RunScript {
    RunsWhen = After
    RunsOnClient = no
    RunsOnFailure = yes
    Command = "/path/to/script %c"
}

into your JobDefs resource so it gets included in all your jobs
automatically. Passing %c (client name) as a parameter allows
you to test for and do slightly different things on certain
clients within your script if necessary. %n (job name) and %e
(job exit status) might be similarly useful.

HTH
T.

-- 
Tilman Schmidt
Phoenix Software GmbH
Bonn, Germany

signature.asc
Description: OpenPGP digital signature

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