[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: commit: ldap configure configure.in



This particular change only affects the development (HEAD) version, not
any released code (yet). It is really only of interest to the active
developers, no one else should be using the HEAD code with real databases.

But anyway, slapcat the old database and slapadd into the new will convert
just fine.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc  
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Volkov Serge

> Hi all!
> 
> How to convert the DB to this backend ??? if old bases in ldbm?
> 
> Begin forwarded message:
> 
> Date: Tue, 15 Jan 2002 16:26:51 GMT
> From: kurt@OpenLDAP.org
> To: OpenLDAP Commit <openldap-commit2devel@OpenLDAP.org>
> Subject: commit: ldap configure configure.in
> 
> 
> Update of /repo/OpenLDAP/pkg/ldap
> 
> Modified Files:
> 	configure  1.418 -> 1.419
> 	configure.in  1.388 -> 1.389
> 
> Log Message:
> Switch the default backend to BDB.
> 
> 
> CVS Web URLs:
>   http://www.openldap.org/devel/cvsweb.cgi/
>     http://www.openldap.org/devel/cvsweb.cgi/configure
>     http://www.openldap.org/devel/cvsweb.cgi/configure.in
> 
> Changes are generally available on cvs.openldap.org (and CVSweb)
> within 30 minutes of being committed.
> 
> 
> 
> 
> 
> -- 
> With best wishes, Volkov Serge		
> Network Administrator/Security Administrator 		
>