FW: commit: ldap/servers/slapd/back-bdb back-bdb.h cache.c config.c init.c proto-bdb.h

["Howard Chu" <hyc@symas.com>]

It occurred to me later that the simpler fix would have been just to no-op
the bdb_cache_entry_lock/unlock functions, just like the ldap_pvt_thread_*
functions are no-op'd in a NO_THREADS build.

  -- 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-commit@OpenLDAP.org
[mailto:owner-openldap-commit@OpenLDAP.org]On Behalf Of hyc@OpenLDAP.org
Sent: Wednesday, September 18, 2002 4:13 PM
To: OpenLDAP Commit
Subject: commit: ldap/servers/slapd/back-bdb back-bdb.h cache.c config.c
init.c proto-bdb.h


Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-bdb

Modified Files:
	back-bdb.h  1.61 -> 1.62
	cache.c  1.10 -> 1.11
	config.c  1.18 -> 1.19
	init.c  1.94 -> 1.95
	proto-bdb.h  1.52 -> 1.53

Log Message:
Fixes for NO_THREADS
	Use a per-env locker ID
	Always set lock_detect, since we allow slapadd etc. concurrently
Also removed unused lock_detect_task code. lockdetect config keyword only
needs <policy>, no <seconds> argument.



CVS Web URLs:
  http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/

http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/back-bdb.h
    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/cache.c
    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/config.c
    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/init.c

http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/proto-bdb.h

Changes are generally available on cvs.openldap.org (and CVSweb)
within 30 minutes of being committed.