Hold after rip feature ?

[Julien Blanc]

> > On Dec 4 01:30 Julien Blanc wrote (shortened):
> > > Is there a way in cups to achieve an "hold after rip" feature ?
> > ....
> > > "lp -H hold" is not a working option now, because it won't do the rip.
> >
> > I didn't test if the following actually works:
> >
> > Set up a raw queue for the printer and let the filtered queue
> > (i.e. the queue with the printer driver which does the rip)
> > print into the raw queue for the printer.
> >
> > Hold the jobs in the raw queue and release them as you like.
>
> Thanks for the quick answer, i'll have a look at that.
>
> > Perhaps you may have to disable printing for the raw queue
> > to hold the incomming jobs there, then change the priority
> > of the jobs in the raw queue and finally enable printing
> > so that the jobs should come out according to the priority.
>
> I looked a bit into the code, and it seems that adding an "hold-after-rip"
> option to lp wouldn't be too much work, even for a newcomer in the code like
> me. I'll try to do that.

For the records, i'll answer to myself.

The two queue systems does the job well, but disabling the printer will prevent them from being ripped in the first queue.

After digging into the code, it appeared that adding the hold-after-rip feature is really non-trivial (as far as i've seen, there's no way to stop a job at one step of the filter processing ?), but i've found another solution. The job-hold-until option can be put at the queue level in the printers.conf file, which seems to work very well.

Thanks for the tip !

Julien