Hello !
Thanks for getting back on this.
Kern Sibbald wrote:
Another more important point that has been brought up is how users can
guarantee that their Run After Job script is unconditionally run so they can
restart their database after shutting it down in the Run Before Job script.
The answer is: the Run After Job is run only when the job terminates
normally, but you may also define a "Run After Failed Job" that will be run
if the job terminates with any error. If both the directives are specified
and they specify the same script, your script will then be unconditionally
called. If you wish to know the exit status, you can pass it as one of the
edit codes on the command line.
[EMAIL PROTECTED] bin]# service bacula-dir start
Starting Bacula Director services: 03-Mar 15:48 bacula-dir: ERROR
TERMINATION at parse_conf.c:834
Config error: Keyword "ClientRunAfterFailedJob" not permitted in this
resource.
Perhaps you left the trailing brace off of the previous resource.
: line 23, col 34 of file
/var/backup/bacula/bin/clients/bernoulli.conf
Client Run After Failed Job = /root/bin/oraup
[FAILED]
Seems it`s not inmplemented for clients yet ? Or do i have to go for the
latest release ? Also the documentation is missing this.
Best regards,
--
Daniel Holtkamp Riege Software International GmbH
System Administration Mollsfeld 10
40670 Meerbusch, Germany Phone: +49-2159-9148-41
mail: holtkamp [at] riege.com Fax: +49-2159-9148-11
--------------------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
