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

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=20
resolved correctly. Downgrading to 3.0.14a "restored"=20
the idmaps. tdbdump showed me the same idmappings,=20
therefor i think winbind wasn't able to read them?

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

The idmap is in a lock idmap tdb file=20

Mit freundlichem Gru=DF,



Dirk Laurenz
Systems Engineer=09

Fujitsu Siemens Computers
S CE DE SE PS N/O
Sales Central Europe Deutschland=20
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@fujitsu-siemens.com
Internet: http://www.fujitsu-siemens.com
http://www.fujitsu-siemens.de/services/index.html
************************************************** ***********************=
******************************************
=20
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba