Hi, 03.07.2009 20:49, Jeff Shanholtz wrote: > > > I’d like to run a script before all my scheduled jobs start and another > one after they all end, as opposed to before/after a single job runs. > I’d like the “after” script to run immediately after the jobs are done, > otherwise I’d just use the Windows task scheduler. I figured I’d be able > to create a “before” job and an “after” job, but it appears that jobs > must perform some actual Bacula task. So is my only alternative to put > the “before” directive in the first job and the “after” directive in the > last job?
No, not necessarily. If I understand you correctly, you'd use two admin jobs: One scheduled a minute before the first backup job, the other a minute after the last backup. Those admin jobs can execute commands like regular jobs - that's their main purpose - and if you set the priority numerically lower and higher, respectively, than the backup jobs, the order should be correct. Arno > > > In other words, these scripts aren’t specific to a particular job so I > want to disassociate them from the individual jobs if possible. > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück www.its-lehmann.de ------------------------------------------------------------------------------ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
