Hi, I've had a problem haunt me a couple of times as I add clients: after a new client/job is added, when the first initial job is run, it is naturally upgraded from Inc to Full. So far, so good. But the problem is that for large jobs, that take more time than one Inc-cycle to finish, the next Inc job gets immediately upgraded to Full (- because there is no *completed* full job yet) as well, and placed in the job queue waiting for MaxClientJobs.
And when the initial job is finished, the "next" Full job(-s) in the queue start, and so on and so on... Is there any way to avoid that, other than keeping an eye on the bconsole, manually Cancelling the pending job stack? Or is it a known bug, fixed in CVS? :o) //conny ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
