> >At least in windows one can kill a print job which has already
> >started[1].

> A bit naughty but I have been known to pull out the cable in the past!

If you mean the data cable, this doesn't even stop the printing (printer
buffer content still gets printed). The power cable/switch does the
trick though. It does however not remove the remaining job data from the
queue! The problem is that once printing has started, cups can't clear
out the USB interface again. Yeah you can remove the job from the queue,
it'll even work if the queue is local[1], but it still doesn't kill the
process which shoves the print data out the USB interface!

Volker

[1] Last time I looked (about 1y ago), for setups where you have a local
queue which forwards to a remote queue, like you always have in an
office/lab, some cups &@$&**@ decided to only give you the status of,
or remove jobs from, the local queue. As the local queue immediately
drains to the remote queue, you can not ever do anything useful!! lprng
does this properly.

-- 
Volker Kuhlmann                 is possibly list0570 with the domain in header
http://volker.dnsalias.net/             Please do not CC list postings to me.

Reply via email to