There must be a better way!
Further to recent threads on problem of stopping bad printout:
problem: printer prints many pages of postscript code. Job won't stop - gives
an error something about permission-client. Same problem can occur when, for
example, printing a 22-page fax and running out of toner in the middle,
printed job on a different printer to save waiting for new (expensive!) toner
catridge: once cartridge is replaced, if job is already spooled to the host
with the printer, it cannot be stopped from the source host.
solution so far: power down printer, delete printer from cups, reinstall and
power up printer. This gets rid of the "unstoppable" job.
remaining problem: Often, the new printer will not run. Error says printer
port lp0 is blocked (or something similar). Now it is necessary to reboot
the host as well.
So, I have two questions:
1/ surely there is a way to delete the spool file directly -- it must be
somewhere. I am not talking about the /var/spool/cups/d* file - deleting
that does not stop a job from printing necessarily. The data evidently
go somewhere else after that.
2/ surely there is some way to unblock the lp0 port without rebooting the
whole system. This isn't windoze.
Any ideas?
--
richard
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
