[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
alock + ldbm in 2.3.21
- To: OpenLDAP <openldap-software@OpenLDAP.org>
- Subject: alock + ldbm in 2.3.21
- From: "matthew sporleder" <msporleder@gmail.com>
- Date: Wed, 12 Apr 2006 15:33:43 -0400
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=p4G1DKUNuJFy9lSWECxCTpPVK9O5UZjSTt0KSg+IUmlTSFI0WcnIFi0nzKZCqneqAkcNgZtHlxRn60N4q0GKhGRyNTw+kde3/Gzv4EtPN0ejDPD947yinDt/cKpCQBqEHJKXd+xu/aH6qS8uCQbbknDNFVongCV1LfyJ8Uzwx78=
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 658149 local6.debug]
ldbm_back_db_open: alock package is unstable; database may be
inconsistent!
Apr 11 15:21:22 labogldir02 slapd[16232]: [ID 100111 local6.debug]
slapd starting
Can I get a status on alock for LDBM?
According to:
http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/alock.c?hideattic=1&sortbydate=0
it looks like ldbm is having some alock rethinks. Should I wait for
ldbm to be re-stabilized in 2.3.x?
Thanks,
_Matt