The failure is just due to the way my startup script (ldap) handles the warning. The warning is the same as before.
config_build_entry: "cn=schema" config_build_entry: "cn={0}core" config_build_entry: "cn={1}cosine" config_build_entry: "cn={2}inetorgperson" config_build_entry: "cn={3}nis" config_build_entry: "cn={4}acs" config_build_entry: "cn={5}ppolicy" config_build_entry: "olcDatabase={-1}frontend" config_build_entry: "olcDatabase={0}config" config_build_entry: "olcDatabase={1}bdb" WARNING: No dynamic config support for overlay ppolicy. config_build_entry: "olcOverlay={0}ppolicy" backend_startup_one: starting "c=US" bdb_db_open: c=US bdb_db_open: dbenv_open(/var/lib/ldap/openldap-data)
Is it true that the above warning does NOT indicate that ppolicy is not successfully loaded, and that in fact everything should be just fine?
Thanks again
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@stanford.edu] Sent: Monday, January 22, 2007 5:19 PM To: Metcalf, Roger; openldap-software@openldap.org Subject: RE: pesky ppolicy problems
--On Monday, January 22, 2007 4:27 PM -0500 "Metcalf, Roger" roger.metcalf@acs-inc.com wrote:
Thanks for the quick response! I'm using 2.3.27 because it
was The Stable
Release when I started this. I'll move to the latest stable release after I get ppolicy
figured out.
Starting slapd: FAILED [root openldap-2.3.27]#
When slapd fais for me, I usually use -d -1 to see why. It generally will tell you right away.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html