From: Kurt P. <k1p...@gm...> - 2005-01-24 21:45:03
|
On Monday 24 January 2005 19:18, Amaury Jacquot wrote: > is there a way to tell cups to start print jobs niced, so that they > don't clog the machine ? This cannont be done on a per-job basis. What you can do, is set job "priority" individually (it is 50 by default) -- but this works only compared to the rest of the jobs. Sending 100 low level priority jobs at the same time will clog the machine the same way. However, there are ways provided by CUPS to control how much overall "CUPS load" you can burden onto the hosting machine. Have a look at http://localhost:631/sam.html and search for these parameters: MaxJobs MaxJobsPerPrinter FilterLimit MaxJobs limits the number of jobs that are current (spooling, printing, or kept on hold) or past (that is which are finished, but kept in the job history) to the value set across all printers. (A big number of MaxJobs can produce a high longer time for cupsd startup, and a higher load/waiting time for commands such as "lpstat -o"). FilterLimit accounts for the "costs" of all concurrent CUPS filter processes. (These costs are defined in the "mime.convs" config files in $CUPSROOT). Cheers, Kurt |