[Samba] Re: Mdk 9.1, samba-LDAP 2.2.8a/3.0b3 (LDAP) can't print to z53

Dragan Krnic dkrnic at lycos.com
Thu Jul 31 22:37:03 GMT 2003

>>>b)link to a cvs diff

>> Huh?

>Something like this:
>Which according to the cvs log:

It's twice the same link, Buchan, but I can understand
the message.

>[f]ixes this. But I don't see a patch in cvs to
>source/rpc_server/srv_spoolss_nt.c that relates to 
>this. So is the fix above sufficient?

There are really 2 bugs. One affects the enumdriver
subcommand and is resolved with the patch you quoted. 
The other is burried deeper in the invocation of 
sys_adminlog and affects the adddriver or setdrivers
subcommand, I'm not sure which anymore. Since I 
considered it somehow superfluous, I extended the 
comment /* BEGIN_ADMIN_LOG */ up to the comment
/* END_ADMIN_LOG */ to include the whole switch loop.

The actual maintainer might have fixed the underlying
defect. I just killed what seemed superfluous to me.

>> Which is really interesting. Can you look up the 
>> section cited in my patch file to see whether 
>> Mandrake patched it on their own or the patch is 
>> already in cvs without a link to it in bugzilla?

>No, we didn't have a patch for this (although you can 
>check for yourself in cvs at 
> http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/SPECS/samba

Huh? I never used cvs. I've administered a big 
ClearCase multi-site but I never touched cvs. Sorry.

>>>So, unless I see an official patch list for 2.2.8a 
>>>(or there is a new release, maybe also fixing the 
>>>problem with cups printers not appearing without a 
>>>restart of smbd) or a transparent way of finding 
>>>which patches should be applied, I won't rebuild 
>>>packages for 5 releases.

>> You're under no obligation to do anything, 
>> especially if you don't have the problem. Your name 
>> just popped up in a thread I shared with Jim for 
>> some reason and I didn't remove it from later 
>> correspondence.
>Well, I maintain samba/samba3 in Mandrake, 

How do you do, Mr. Milne?

>and a number of people have implied that there are 
>patches for 2.2.8a which should be applied (and I
>would like to see the one for the cups printer list 
>myself) ... but there is no list available of those 
>that should be applied ... so distributors must guess 
>from cvs logs what should be applied (which IMHO
>is not the ideal situation for the samba team if they 
>want their software to work out-the-box on the 
>majority of deployments). And with a potential switch 
>to samba-3.0.0 just before the upcoming 9.2, I would
>prefer not to have to go chasing after patches for 
>2.2.8a (I have enough to test with samba3).

I can sympathize with samba team that they're too busy
following up on 3.betas but at the same time, this 
kind of bug can't be ignored. It's making people 
almost criminally insane. Someone was yelling
"How I HATE samba printing" right in his subject line.

I should have fixed it earlier, since it first didn't
abide by the documentation in 2.2.5, but it was so much
easier to kludge the clients to live with it.

Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!

More information about the samba mailing list