Antoine Durr wrote:
> So I whipped up something this afternoon. It's pretty simplistic, and
> I'm curious as to where it might fall flat on its nose.
BTW, if all you're looking to do is have jobs just be FIFO,
you can set up the submit scripts so that each time a job
is submitted, it submits with a successively lower priority.
I've helped some folks do this by keeping a running priority
count in a little text file on the network drive, and have the
submit scripts grab the value from the file, decrement its contents,
and use that as the job's submit priority.
Each day at 5am, a crontab resets the value in the file to 999, eg:
echo 999 > /your/server/rushfiles/next-priority.txt
..this way each morning when folks get in, the priority for
new jobs starts at the top again.
This assumes jobs aren't still running from the day before,
but that's usually the case. And even if they were, they'd simply
move aside to allow the new jobs of the day to run, and 'last nights jobs'
would get cpus when there are idle procs.
This would avoid the need for a "watcher" script.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|