| 1 |
Jigme Datse Rasku schrieb: |
| 2 |
> This seems like it should be possible. The potential issue would be how to ensure a whole job is printed, before a new job is sent. With a single cups process sending to the printer, it should be able to print as jobs get prepared. But configuring such might not be possible with current setup... |
| 3 |
|
| 4 |
I would expect CUPS to do that out of the box. Once a job has been |
| 5 |
processed, it can be sent to the printer as a whole and it won´t be |
| 6 |
possible for other jobs to be printed in between. |
| 7 |
|
| 8 |
Since CUPS doesn´t seem to do it out of the box, maybe there´s a |
| 9 |
setting I need to change to make it do this? |
| 10 |
|
| 11 |
|
| 12 |
> |
| 13 |
> |
| 14 |
> On Sep 13, 2016 09:50, "hw" <hw@×××××.de <mailto:hw@×××××.de>> wrote: |
| 15 |
> |
| 16 |
> |
| 17 |
> Hi, |
| 18 |
> |
| 19 |
> is it possible to make cups print a job while another job is still |
| 20 |
> being processed, on the same printer? |
| 21 |
> |
| 22 |
> Processing a large job can take quite some time, and the printer is |
| 23 |
> idle while the large job is being processed and other, smaller jobs, |
| 24 |
> are idly waiting in the queue for the large job to finish. |
| 25 |
> |
| 26 |
> I want like a maximum of 20 jobs being processed at the same time so |
| 27 |
> that the printer can print the ones that have already been processed |
| 28 |
> immediately when their processing has finished. |
| 29 |
> |
| 30 |
> Why should cups be limited to use only one CPU? |
| 31 |
> |
| 32 |
> |
Archives