On Wednesday 26 October 2005 14:16, Arno Lehmann wrote:
> Hello,
>
> On 26.10.2005 13:41, Marek Simon wrote:
> > I have a feature request for next version
> > There are Client Before and After commands, its usage is obvious. But
> > when the backup fails (not enough space etc), the After command will not
> > run and the client dont know, the backup is (even unsuccesfully)
> > finished. So I would like to have another parameter, which would the
> > director run on client, when the backup fails. I think it is better then
> > some obscur scripts which check it with some bmonitor.
> > Marek Simon
>
> *If* something like that should be implemented, i'd rather suggest
> simply changing Baculas behaviour so that Run After Job scripts are also
> executed in case of job failure.
I would be reluctant to do that because it might break a lot of user's
existing jobs ...
> The job status could be fed to the script as a parameter.
Personally, I would rather go the Python scripting route as it keeps Bacula
clean and lean, and at the same time opens a whole lot more possibilities for
the users.
If I see that users just cannot "get" or tolerate Python scripting, then
falling back to Phil's suggestion would be a solution.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
