[cups.general] jobs passed to printer too quickly

[nancy lin]

Hi Michael

Actually I used socket://x.xxx.xxx.xxx:9100 first.  is that what you mean? 
  The behaviors are the same for either one.   The printer is HP 4100.  But 
this happens w/ all of my printers.  They are HP color 3800, HP 4100, HP 
4350, and an HP 2100.

In terms of behavior, I'm slowly going through all of the mailing list. 
There was a mention that cups consider all jobs as being done when the 
connection closes (it receives the last byte).  I have 60 clients and I"m 
configuring them to all point to one cups server so that the logs are all 
at one place and I can do print account using pykota.  (havn't installed 
pykota yet).

Would that make the difference?  I don't think it does as I've tried just 
printing a test page from the web interface and the job still gets 
processed way too quickly.  But supposing I print a big huge PDF file or 
something.  Does cups consider the job to be done when it has finished 
transmitting the job to my printer?  Or does it consider it to be done when 
it gets an end of job from the printer?

thanks
nancy

Michael Sweet wrote:
> nancy lin wrote:
>> Hello
>>
>> Sorry.  I'm using RHEL4's cups 1.1.22.0.rc1.9.10.
>>
>> THe URL is something like ipp://xx.xxx.xxx.xxx./ipp/4100
> 
> You might try using socket://xx.xxx.xxx.xxx instead.
> 
>> I'm using the driver that comes w/ RHEL.  I think it's the HP Laserjet 
>> driver.
> 
> and the printer you are printing to is ???
> 
>> Should I upgrade to 1.2.2?
> 
> At this point I can't say whether that will help.  1.1.22 is fairly
> recent and stable...
> 
>> lpstat -t (from LPRng) was able to display both active jobs and the 
>> last 2 completed jobs.  Will cups's lpstat be able to do that as well?
> 
> No, we don't have an option/mode for that - you can display the
> active, completed, or all (in CUPS 1.2.x) jobs via the -W option.
>