Gavin Henry: > The OpenLDAP stuff on this page: > > > http://us4.samba.org/samba/docs/man/Samba-Guide/happy.html > > > is not the preferred backend, i.e. ldbm, it really, really needs to be > bdb. > > See: > > > http://www.openldap.org/faq/index.cgi?_highlightWords=bdb%20ldbm&file=108 > 5
Pointing LDAP users toward OpenLDAP.org will hopefully get them to see that not only ldbm as backend is considered obsolete and is deprecated, but also that OL 2.0 is considered obsolete, 2.1 is obsolescent and deprecated and the latest stable version is 2.2.23. Which uses Sleepycat BDB 4.2.52 mandatorily. [...] > I feel we are not doing the Samba community justice, if we are telling > them to use lbdm. ldbm as backend will ultimately seize up on production rigs, for a number of reasons. So will BDB 4.1, though for different reasons (I've been through it all myself). OpenLDAP 2.2.13 and higher with (patched) BDB 4.2.52 will keep on running for months without attention, even after forced power-downs or -outages, with all of the advantages that you cite. However, use of BDB 4.2.52 requires specialist configuration (DB_CONFIG) for it to work at all satisfactorily. Which brings me back to my own bugbear: Samba 3 people who want to use the ldapsam DB backend should first and foremost be LDAP specialists, only subsequently adapt their Samba installation to their already successful LDAP implementation. I don't see how the Samba people can write all this up in the standard docs and there is no single HOWTO on the subject. --Tonni -- mail: [EMAIL PROTECTED] http://www.billy.demon.nl -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
