David Hatcher wrote: > [snip] > > I just realized those four jobs that were strangely canceled had a > priority of 11. All the jobs but the last six have a priority of 11 > (and one job as a priority of 10, but that one finish early, in fourth > place). The last six have priorities of 13, 13, 13, 13, 14, and 15. Is > this a bug? Since eight jobs with a priority of 11 were all scheduled > to run Friday at 7:00 PM, did Bacula think these eight jobs actually > started at 7:00 PM Friday and then killed all remaining jobs after 27 > hours. I'm under the impression the "Max Start Delay" option counts > when a job actually started and not from when the job was scheduled to > start. > > -Dave
It sounds like you could try assigning a unique priority to each job, say 10 through 25, leave all the other settings the same and see if the jobs get canceled again. Alex ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
