John Drescher wrote: > On Mon, Jan 19, 2009 at 6:39 PM, Ryan Novosielski <novos...@umdnj.edu> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Jean Gobin wrote: >>> Hello, >>> >>> I'm wondering whether a "window" functionnality exists in the current >>> version of Bacula. >>> >>> I explain: we have several jobs executing. And for some reasons, one of >>> them was delayed until business hours. The only problem is that this job >>> starts by executing a script which shuts an application down before moving >>> files, then restarts it. That was not truly welcome during the day ... >>> >>> Do you think a "Window" statement, specifying start and end times for a job >>> to execute would come in a handy for this? >>> >>> Something like: >>> >>> window <start hour> <stop hour> <allowed days> >>> >>> Where <start hour> and <stop hour> would be formatted like hh:mm:ss, and >>> <allowed days> would be [Mon|Tue|Web|Thu|Fri|Sat|Sun], to take into account >>> possible maintenance days. >>> >>> This new thread opened as per Bruno F. request. >> It would make life a little easier, yes, but there are similar existing >> options to do the same time. Max Run Time, Max Wait Time, and maybe one >> other all come to mind. Check them out. >> > > Or check the time in the run before script that stops the services. > Return an error and the job will not run.
Simple for the win.... -- Dan Langille BSDCan - The Technical BSD Conference : http://www.bsdcan.org/ PGCon - The PostgreSQL Conference: http://www.pgcon.org/ ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
