[Samba] WINBIND idmap and tdbfiles while upgrading to 3.0.20a

[Dirk.Laurenz at fujitsu-siemens.com]

Hello everybody,

had anyone of you problems with winbind and tdbfiles, when
upgrading from 3.0.14a to 3.0.20a?

The Symptom was:
	After upgrading to 3.0.20a the idmapping was corrupt.
	Although 3.0.20a runs fine, none of the idmaping was 
	resolved correctly. Downgrading to 3.0.14a "restored" 
	the idmaps. tdbdump showed me the same idmappings, 
	therefor i think winbind wasn't able to read them?

Has anyone an idea why this happened? Has anyone had this 
problem too? There're no entries in the log concering this.

The idmap is in a lock idmap tdb file 

Mit freundlichem Gruß,



Dirk Laurenz
Systems Engineer	

Fujitsu Siemens Computers
S CE DE SE PS N/O
Sales Central Europe Deutschland 
Professional Service Nord / Ost

Hildesheimer Strasse 25
30880 Laatzen
Germany

Telephone:	+49 (511) 84 89 - 18 08
Telefax:	+49 (511) 84 89 - 25 18 08
Mobile:	+49 (170) 22 10 781
Email:	mailto:dirk.laurenz at fujitsu-siemens.com
Internet:	http://www.fujitsu-siemens.com
            http://www.fujitsu-siemens.de/services/index.html
*******************************************************************************************************************