Hi Tim,

The next print job will clear any previous canceled print job. For PCL
Inkjets each print job begins with a 1.5k null header. This will clear
any outstanding partial print job. On newer printers and lasejets the
1.5k null header is not required.

This is current HPLIP functionality. Its on my list to add job cancel
support to hpiod. Currently hpiod detects when the client socket goes
away and performs device cleanup. The current device cleanup can be
expanded to printer job cleanup if a print job is active.

Given the current job cancel support I have not given the job cancel
enhancement high priority. Are you getting different feedback? Is the
current job cancel support a problem?

-dave

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf 
> Of Tim Waugh
> Sent: Friday, December 08, 2006 9:22 AM
> To: hplip-devel@lists.sourceforge.net
> Subject: [HPLIP-Devel] Job cancellation and the 'hp' CUPS backend
> 
> 
> The 'hp' CUPS backend from HPLIP doesn't handle SIGTERM, and 
> so when a job is cancelled the device is not reset.
> 
> How can this be fixed?
> 
> Tim.
> */
> 
> 

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
HPLIP-Devel mailing list
HPLIP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hplip-devel

Reply via email to