> On 22/11/05, Kern Sibbald <[EMAIL PROTECTED]> wrote: > > > 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. > > Would this take into account people who want to run scripts > both before *and* after josbs? For example, perhaps stopping > a database instances before the Job then starting afterwards? > > Will.
Why not adopt a init-like model where the same script is used in both cases, but it is passed a Before/After argument on invocation, eg: If a script is defined for a job, Bacula calls the script as 'action-script before' before the job runs, and 'action-script after' after the job runs. The script parses the argument and runs a case statement with options for 'before' and 'after'. If you don't want anything done before the job runs, the "before" section is 'exit 0'. If you don't want anything done after, the after section is 'exit 0'. Avoids cluttering the command space with a zillion options, and puts the smarts in the script instead of making Bacula deal with it. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
