[Samba] SLow cups printing, lots of get-printer-attributes

[Martin Zielinski]

Hello,

This is the result of asking cups for a comment and location string to 
sync them between cups and samba.
I've allready asked the samba-team to replace it with a more general 
approach but got no response until now.

As a workaround, please set the comment and location string of every 
printer from your windows client in the printers and faxes section. When 
samba has both strings in its ntprinter.tdb database, it will no longer 
ask cups for them.

If you compile samba yourself, you can search in nt_printing.c for the
HAVE_CUPS defines and comment out the part.

Bye,

Martin

Emmanuel Lacour schrieb:
> On Fri, Dec 14, 2007 at 03:59:02PM +0100, Emmanuel Lacour wrote:
>> Hi all,
>>
>> I encounter a problem here on a samba PDC with 97 cups printers.
>>
>> When on a windows client, I click right on a printer, then select
>> "properties", it tooks about 12 secondes to open.
>> When from a spreadsheet such as M$ Excel I click on print, then try to
>> select an imprimante from my pdc, it tooks about 30 seconds.
>>
>> I did some debugging, and with an strace on the smb process, found that
>> for my first test (printer properties), samba ask cups 25 times per
>> printers for printer attributes (I also found in cups a lot of
>> Get-printer-attributes successful-ok).
>>
>> below an exemple of this call from strace.
>>
>> is there someone who know why samba test each printer 25 times ?
>> is there someone who knwo why samba ask for informations on other
>> printers when I select a defined printer ?
>>
>>
>> Except this give me really slow printing management, printing itself is
>> working fine ... just slow.
>>
>>
>> Thanks for any hint/help :)
>>
> 
> 
> I did some tests and found that it results from a change between 3.0.24
> and 3.0.25 and it's stil there in 3.0.28.
> 
> The strace for 3.0.24 is really shorter than newer versions as it just
> open the right printer and does not try to access all informations of
> all printers.
> 
> Ther is a lot of changes on the printing code between 3.0.24 and 3.0.25,
> but I will try to study it a little bit :/
>