On 06/06/2018 08:48 AM, Donna Hofmeister wrote:
> In a job{} definition, is it possible/advisable/wise to have multiple
> RunAfterJob statements?
Hello Donna,
Yes, it is possible.
> If so, does N+1 wait on N to complete? - d
Yes.
However, there is not a 100% guarantee that they will be run in the order you
have them listed in the configuration. Most likely they will, but not
absolutely 100%.
When it comes to RunScripts{} - RunsWhen=(before|after), or the more simple
RunBeforeJob and RunAfterJob ones, I tend to agree with Dan on this and I will
usually have just one before and/or after, and each will call a script.
In the script I can guarantee that the commands I wish to run are run in the
precise order I want, and I can do whatever error checking I think is
necessary, and exit appropriately to fail the job if necessary. ie: dump a
database in a RunBeforeJob script , but it fails, so the job should fail.
If the order is not a precise requirement, then using multiple RunAfterJob
commands is fine though.
Best regards,
Bill
--
Bill Arlofski
http://www.revpol.com/bacula
-- Not responsible for anything below this line --
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
