[cups.general] Problem after update from 1.3.10 to 1.4.1 withjob queue

[Ralf Aumueller]

Hallo,

I wait more than 1 hour.

Best regards,
Ralf

(The compile options were: --enable-ssl --disable-gssapi --disable-ldap)

Michael Sweet wrote:
> How long did you wait after the jobs completed?  CUPS keeps completed  
> jobs for at least 60 seconds to allow clients to get the job completed  
> status...
> 
> On Nov 4, 2009, at 1:36 AM, Ralf Aumueller wrote:
> 
>> Hello,
>>
>> today I did an CUPS update from 1.3.10 to 1.4.1 (self-compiled CUPS  
>> on Solaris
>> Sparc 10. Just made a "make install" over the old installation).
>>
>> Printing works fine but I have a problem with the "Jobs"  
>> information. I disabled
>> the job history with the following options in cupsd.conf (this works  
>> fine with
>> 1.3.10):
>>
>> ...
>> PreserveJobHistory Off
>> PreserveJobFiles Off
>> ...
>>
>> But when I use the command "lpstat -W all" or use the web-frontend  
>> ("show all
>> jobs") I see all jobs since the update. Even the control file are  
>> there under
>> .../var/spool/cups/c*. In the web-frontend the status of the jobs is  
>> "pending
>> since" but all the jobs were printed fine.
>>
>> (All printers are HPs and the connection type is socket:9100)
>>
>> Any hints?
>>
>> Best regards,
>>
>> Ralf
>> _______________________________________________
>> cups mailing list
>> cups at easysw.com
>> http://lists.easysw.com/mailman/listinfo/cups
> 
> ___________________________________________________
> Michael Sweet, Senior Printing System Engineer
> 
> 
>