Thank you

I'll have to read about this, I'm not sure if it will do what I want.  Specifically, the script is designed to say whether a job should be run or not, but if it is not supposed to run, I won't want an error generated, since it isn't an error.



JBB

On 6/15/2013 6:18 AM, Ana Emília Machado de Arruda wrote:

Hi Jonathan,

If you want to run the script, before job, and don´t have the job canceled if script fails, you can use the "RunScript" directive instead. With options "Run When = before" and "Fail Job On Error = no".

RunScript {
    RunsWhen = Before
    FailJobOnError = No
    Command = "/yourpath/yourcommand"
}

Regards,

Ana

On Fri, Jun 14, 2013 at 3:49 PM, Jonathan Bayer <linuxgurugamer AT gmail DOT com> wrote:

The manual states the following:

Run Before Job = <command> The specified command is run as an external program prior to running
the current Job. This directive is not required, but if it is defined, and if the exit code of the program
run is non-zero, the current Bacula job will be canceled.

So when a job is canceled, is it reported as an error?  I need to know because I'm thinking about using this mechanism to control job schedules, but if it is reported as an error then our reports will also show errors, which we don't want to do since we show them to upper management.

Thanks in advance


JBB

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users