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

RE: commit: ldap/servers/slapd/back-bdb trans.c Makefile.in add.c delete.c modify.c modrdn.c passwd.c proto-bdb.h

This sounds a bit on the heavyweight side. I think using DB_LOCK_YOUNGEST for
deadlock resolution should handle most problems. It should ensure that
operations complete in the same order they were received, and thus should
also fix the out-of-order replog problem as well.

  -- 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
> jongchoi@OpenLDAP.org
> Sent: Tuesday, July 01, 2003 2:55 AM
> To: OpenLDAP Commit
> Subject: commit: ldap/servers/slapd/back-bdb trans.c Makefile.in add.c
> delete.c modify.c modrdn.c passwd.c proto-bdb.h
>
>
> Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-bdb
>
> Modified Files:
> 	Makefile.in  1.21 -> 1.22
> 	add.c  1.78 -> 1.79
> 	delete.c  1.82 -> 1.83
> 	modify.c  1.80 -> 1.81
> 	modrdn.c  1.113 -> 1.114
> 	passwd.c  1.56 -> 1.57
> 	proto-bdb.h  1.79 -> 1.80
> Added Files:
> 	trans.c  NONE -> 1.1
>
> Log Message:
> Berkeley DB congestion avoidance
>
>
> 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/trans.c

http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/Makefile.in
    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/add.c
    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/delete.c
    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/modify.c
    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/modrdn.c
    http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/back-bdb/passwd.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.