The Friday 2003-12-26 at 07:13 -0500, Kenneth Schneider wrote:
First most printers have builtin buffers which will not be flushed when you cancel the print job.
I know. Even so, there is a command to flush it. And in any case, that would account for a few centimiters of graphical output, but not a full dozen of pages full of graphics. Its not so big a memory (canon 4000, inkjet type).
Second:
If you are using cups you should be using lpstat -t (or -o) to list the print jobs.
"lpq -a" lists them all as well. lpstat gives more info, but the print jobs are the same. See: cer@nimrodel:~> lpstat -o lpg-334 cer 6406144 Fri 26 Dec 2003 02:15:04 PM CET cer@nimrodel:~> lpq -a Rank Owner Job File(s) Total Size active cer 334 (stdin) 6406144 bytes
Use cancel <print job#> to cancel the print job and if need
As I said yesterady, it doesn't work. Job is cancelled, job quee is empty, but continues printing, nevertheless.
be power cycle the printer to flush its buffers.
Doesn't work. As soon as it comes again on line, it continues printing, but worse: this time it prints garbage in many pages, because the graphics configuration (ESC codes) at the start of a line or job was erased from memory, and the printer can no longer interpret properly what is comming from the computer. You did not read carefully my post: I said that even after cancelling the job and stopping cups, there remains a running task (belonging to root) that continues printing till reboot or manual kill. This program should have been stoped by cups, but it doesn't. -- Cheers, Carlos Robinson