Greg Ercolano wrote:
> ..and then let the 'watcher script' bump the =0 values (cpu caps)
> up and down with the 'rush -cp' command, eg:
>
> rush -cp +a=0 +a=3 somejob.123
Oops, that should have been:
rush -cp +a=0@1 =3@1 somejob.123
^^^^^^ ^^^^
Old New
..the priorities need to be specified too, because there can be multiple
priority groups. (Your polling script would first get the 'old' cpu/pri
info from the 'rush -lc' report)
For more info on the -cp (change priority and cpu cap) command, see:
http://www.seriss.com/rush-current/rush/rush-command-line-options.html#-cp
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Fax: (Tel# suppressed)
Cel: (Tel# suppressed)
|