Hello,

I have added the following feature request to the projects file:

Item 19:  Implement new {Client}Run{Before|After}Job feature.
  Date:   26 September 2005
  Origin: Phil Stracchino <phil.stracchino at speakeasy dot net>
  Status:

  What:   Some time ago, there was a discussion of RunAfterJob and
          ClientRunAfterJob, and the fact that they do not run after failed
          jobs.  At the time, there was a suggestion to add a
          RunAfterFailedJob directive (and, presumably, a matching
          ClientRunAfterFailedJob directive), but to my knowledge these
          were never implemented.

          An alternate way of approaching the problem has just occurred to
          me.  Suppose the RunBeforeJob and RunAfterJob directives were
          expanded in a manner something like this example:

          RunBeforeJob {
              Command = "/opt/bacula/etc/checkhost %c"
              RunsOnClient = No
              RunsAtJobLevels = All       # All, Full, Diff, Inc
              AbortJobOnError = Yes
          }
          RunBeforeJob {
              Command = c:/bacula/systemstate.bat
              RunsOnClient = yes
              RunsAtJobLevels = All       # All, Full, Diff, Inc
              AbortJobOnError = No
          }

          RunAfterJob {
              Command = c:/bacula/deletestatefile.bat
              RunsOnClient = Yes
              RunsAtJobLevels = All       # All, Full, Diff, Inc
              RunsOnSuccess = Yes
              RunsOnFailure = Yes
          }
          RunAfterJob {
              Command = c:/bacula/somethingelse.bat
              RunsOnClient = Yes
              RunsAtJobLevels = All
              RunsOnSuccess = No
              RunsOnFailure = Yes
          }
          RunAfterJob {
              Command = "/opt/bacula/etc/checkhost -v %c"
              RunsOnClient = No
              RunsAtJobLevels = All
              RunsOnSuccess = No
              RunsOnFailure = Yes
          }

  Why:    It would be a significant change to the structure of the
          directives, but allows for a lot more flexibility, including
          RunAfter commands that will run regardless of whether the job
          succeeds, or RunBefore tasks that still allow the job to run even
          if that specific RunBefore fails.

  Notes:  By Kern: I would prefer to have a single new Resource called
          RunScript, and within that resource an additional directive:

            RunBeforeJob = Yes|No

          If no, it runs it after the job.


-- 
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. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to