[cups.general] Re: Stop all jobs, NOW!

Felix E. Klee felix.klee at inka.de
Mon Aug 30 09:17:53 PDT 2004


On Mon, 30 Aug 2004 18:06:09 +0200 C.Lee Taylor wrote:
> 	"man cancel" on my FedoraCore2 explains that cancel -a will remove all 
> jobs from select print ...

But - as lprm - it may leave stray jobs accessing the device the printer
is connected to:

[...]> lpr *.ps
[...]> lpq
hplj1100 is ready and printing
Rank    Owner   Job     File(s)                         Total Size
active  root    248     uv10.ps                         6005760 bytes
[...]> cancel -a
[...]> fuser /dev/lp0
/dev/lp0:             8658

>  >This may leave the printers in an inconsistent state. But that flaw is
>  >acceptable and even somewhat intended (better stop now, than print more
>  >pages).
> 	I have had a few times when a jobs starts to spool, and a bright user 
> cancel's the job on the printer, but that is only what has been spool, 
> then I too get plenty pages just coming out ... I was wondering if there 
> might be a way to tell the remote printer to reset after canceling all 
> the jobs?

As I understand it, here's the process to stop printing immediately and
have the printer in a consistent state afterwards:

1. Turn the printer off between page feeds.
2. Run "lprm - -P <destination>".
3. Kill CUPS processes still accessing the device the printer is
   connected to, e.g. with "fuser -k /dev/lp0".
4. Turn the printer back on.

> 	Somebody post just a few messages ago
> 
> 	/usr/bin/enable `lpstat.cups -p | awk '{print $2}'`
> 
> 	But this does not work on my system. I think there might be a problem 
> with the awk part ...

That would just instruct the CUPS to accept jobs for all destinations. I
don't know how that could solve your problem.

Felix





More information about the cups mailing list