Dear List,
Can anyone please tell me how to check which database is being used by our openLDAP?Please di Also please advice me whether we can use the openldap packages that come along with O.S. Because I have seen people advicing not to use openLDAP RPms that come with O.S
Waiting for help.....
Warm Regards, Padmavathi. =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Padmavathi Dt wrote:
Dear List,
Can anyone please tell me how to check which database is being used by our openLDAP?Please di Also please advice me whether we can use the openldap packages that come along with O.S. Because I have seen people advicing not to use openLDAP RPms that come with O.S
Waiting for help.....
Warm Regards, Padmavathi.
We're going to need some more information to answer your question.
Which branch of openLDAP are you intending to use, which operating system do you use .etc
Regards,
Andy
Define "which database"? I mean, "lsof" is good...
BDB library version? Start up a slapd that's configured with a bdb/hdb backend with -d trace.
What backends you're using? Search under cn=config.
As for using vendor supplied packages...generically, and this is much bigger than OpenLDAP:
You should only use vendor supplied products if you are confident that the vendor supplies products intending the use case that you envision. Attempting to use products outside of their intended deployment, quite often, results in significant amounts of pain for both vendor and customer.
As a specific example, Red Hat's RHEL product does NOT intend the use case of an OpenLDAP server, so that would be a bad match without additional suppliers (either rolled yourself or through a commercial offering such as Symas).
On Mon, 31 Mar 2008, Padmavathi Dt wrote:
Can anyone please tell me how to check which database is being used by our openLDAP?Please di Also please advice me whether we can use the openldap packages that come along with O.S. Because I have seen people advicing not to use openLDAP RPms that come with O.S
Waiting for help.....
On Monday 31 March 2008 10:20:05 Padmavathi Dt wrote:
Dear List,
Can anyone please tell me how to check which database is being used by our openLDAP?
Firstly, it is impossible that you are using db4.6 with OpenLDAP 2.2, OpenLDAP 2.2 (and 2.3) don't support db4.6. Secondly, you can check with tools such as ldd which shared library the slapd binary was linked to. Which in your case will most likely be the copy of 4.2 shipped in the RHEL4 OpenLDAP 2.2 packages.
Or, you could just have told us that you were running RHEL4, and we could have told you.
Please di Also please advice me whether we can use the openldap packages that come along with O.S.
Depends on the OS.
Because I have seen people advicing not to use openLDAP RPms that come with O.S
Mainly because they are too old.
Regards, Buchan
--On Monday, March 31, 2008 5:44 PM +0200 Buchan Milne bgmilne@staff.telkomsa.net wrote:
On Monday 31 March 2008 10:20:05 Padmavathi Dt wrote:
Dear List,
Can anyone please tell me how to check which database is being used by our openLDAP?
The "directory ..." line(s) in slapd.conf tell slapd which database(s) are to be used.
As you noted previously (in the thread "Slapd Not getting started after changing the "directory" value in slapd.conf!!!!!!!"), you had installed OL 2.4, and created a database in /usr/local/var/openldap-data. You then downgraded to 2.2, and *changed* your slapd.conf for 2.2 to point to /usr/local/var/openldap-data instead of its old path /var/lib/ldap, which means that now OL 2.2 is looking at the database that 2.4 left behind. Fix your "directory ..." line(s), or remove the old database in that location and start fresh.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-software@openldap.org
-
Aaron Richton -
andy -
Buchan Milne -
Padmavathi Dt -
Quanah Gibson-Mount