Arno Lehmann wrote:
Hello,
Andrei Mikhailovsky wrote:
Hello
after reading the manuals, I couldn't find a solution to my question. Is
it somehow possible to skip higher priority jobs and move to the lower
once if the client with a higher priority is not available.
No, that's not possible.
Even canceling the jobs is not helpful because the cancel command
still needs to wait for the client to time-out.
Hi,
That's make me thinking of a possible enhancement in the (re-)scheduling
of jobs.
The problem I have met one or two times is that for one reason or
another a job could not be run
(missing free volumes in pool in my case), all the jobs with lower
priority won't be runned.
I tried to play with Rescheduling parameters but with no success as the
failed job is rescheduled
with the same priority, so if the problem can't be resolved for the next
tries, all planned jobs after
this one won't be done to... quite annoying
Isn't it possible to add something like a "Reschedule Priority Change =
(int)" parameter that
will increase the priority of the job when it is rescheduled, then it
would be placed at the end of the
queue and others jobs could be runned normally ?
But perhaps I am missing something in the Rescheduling of jobs...
Cheers,
Yann
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
