[cups.general] how to allow only one job at a time (and queue everything else)?
Tomasz Chmielewski
mangoo at wpkg.org
Mon Oct 15 02:45:23 PDT 2007
I have a rather slow device that serves as a tiny domain controller and
a print server (64 MB RAM, 266 MHz ARM CPU).
As printers used with this device don't support PostScript, CUPS have to
filter everything through foomatic/ghostscript.
It works fine (read: slow, but bearable) if users schedule only one
print job. If they schedule more jobs at the same time, this whole
filtering through foomatic/ghostscript is so slow, that printing is very
very slow, users print the documents once again, which slows the things
down even more etc.
This is because running multiple foomatic/ghostscript filters on this
small device at the same time is painfully slow.
Is there a way to configure CUPS so that it runs only one filter job at
any given time? And, if there is a second print job, just queue it, and
wait till the filter for the first print job is done?
I understand there is a "MaxJobs number" directive, but I'm not sure if
it will reject any further jobs, or just queue them - I wouldn't like to
test it on my users ;)
--
Tomasz Chmielewski
http://blog.wpkg.org
More information about the cups
mailing list