openldap-devel

openldap-devel@openldap.org

1418 discussions

Privileged connections in back-ldap/back-meta
by Pierangelo Masarati 23 Dec '06

23 Dec '06

I'm facing the problem of having too many threads operating on the same privileged connections in back-ldap/back-meta, which seems to cause poor scalability. This mainly occurs because we want all operations to be performed as a privileged identity with proxyAuthz. For this purpose I plan to move privileged connections out of the connection AVL tree into ldapinfo_t, so that we save a search in the tree, and keep multiple instances of privileged connections in a LDAP_TAILQ structure of fixed maximum length to use them round-robin. Each type of privileged connection uses a dedicated list, so in our case we basically keep two lists: one for the privileged user and one for binds, which are now serialized into one privileged connection since all subsequent operations use proxyAuthz. A prototype is being tested, which doesn't work too bad (scalability did not dramatically improve yet, so there might be other bottlenecks, but at least some repeatable transient hangs disappeared). Comments? p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

2 1

Re: Lifetime and Documenting of LDAP_DEPRECATED, outside ldap.h
by Kurt D. Zeilenga 20 Dec '06

20 Dec '06

At 06:35 AM 12/20/2006, Gavin Henry wrote: >> Is there a date set that LDAP_DEPRECATED will not be supported anymore? No. >> And should we (docs team) put something on Faq-O-Matic (devel section), or >> in the new devel guide (once an outline/template has been put in place) >> that presents the "Best Practice" for updating their code? Personally, I think it would be better to focus the limited documentation time/energy we have toward documenting non-deprecated code (and discussing how to write clients using non-deprecated code). But as I've noted before, (code and documentation) developers should work on what they need/want... and, if its generally useful, it will find its way into OpenLDAP Software (and/or other materials provided by the Project). That is, don't let my (or other statements) stop anyone from working on what they need/want. -- Kurt

2 1

Lifetime and Documenting of LDAP_DEPRECATED, outside ldap.h
by Gavin Henry 20 Dec '06

20 Dec '06

Dear All, We've been working on some LDAP client code for other Open Source projects and most of them, as well as Linux Distros define LDAP_DEPRECATED to keep the code working etc., as they haven't been updated for the new libs. Is there a date set that LDAP_DEPRECATED will not be supported anymore? And should we (docs team) put something on Faq-O-Matic (devel section), or in the new devel guide (once an outline/template has been put in place) that presents the "Best Practice" for updating their code? Or should we leave it up to them to read over ldap.h, as Kurt put: /* deprecated, please use foobar function */ in it. Thoughts? Thanks, Gavin. -- Kind Regards, Gavin Henry. Managing Director. T +44 (0) 1224 279484 M +44 (0) 7930 323266 F +44 (0) 1224 824887 E ghenry(a)suretecsystems.com Open Source. Open Solutions(tm). http://www.suretecsystems.com/

1 1

Re: commit: ldap/servers/slapd/back-ldap init.c bind.c
by Pierangelo Masarati 19 Dec '06

19 Dec '06

ando(a)OpenLDAP.org wrote: > Log Message: > (almost) blind fixes to ITS#4782 > ldap_back_is_proxy_authz() should be fixed now; monitor should be fixed as well, I'll check later with all backends built as modules. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Cancel operation in RE23?
by Michael Ströder 19 Dec '06

19 Dec '06

HI! Is the cancel operation already supported in RE23? It seems so (playing around with it with python-ldap). But supportedFeatures in root DSE does not contain 1.3.6.1.1.8. RFC 3909 states: Servers SHOULD indicate their support for this extended operation by providing 1.3.6.1.1.8 as a value of the 'supportedExtension' attribute type in their root DSE. A server MAY choose to advertise this extension only when the client is authorized to use it. Ciao, Michael.

2 2

Re: commit: ldap/servers/slapd/overlays rwm.c
by Pierangelo Masarati 17 Dec '06

17 Dec '06

hyc(a)OpenLDAP.org wrote: > Log Message: > Fix callback handling > There seems to be many problems passing test047. I'm fixing a couple of them, but more remain. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

1 0

Re: commit: ldap/servers/slapd/overlays rwm.c
by Pierangelo Masarati 17 Dec '06

17 Dec '06

hyc(a)OpenLDAP.org wrote: > Log Message: > Remove redundant search cleanup > Howard, note that among the issues in slapo-rwm there's the fact that it's attaching a callback structure on the thread's private data instead of malloc'ing (and freeing) it when required. As a consequence, this may prevent slapo-rwm from being called more than once in an operation execution sequence, because it could result in an endless loop or unexpected execution sequences. In fact, when used with a regular database, multiple calls shouldn't occur (one would need to explicitly add more than one instance of slapo-rwm on the same database, which makes little sense). However, gluing more than one database which independently needs slapo-rwm is one such case of multiple calls in one thread execution. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

2 3

Re: commit: ldap/servers/slapd daemon.c slap.h aclparse.c acl.c
by Kurt D. Zeilenga 17 Dec '06

17 Dec '06

This change is non-portable. On FreeBSD 4, the s6_addr_32 is only defined for use in the kernel. IIRC, only s6_addr is standard. At 04:11 PM 12/14/2006, ando(a)OpenLDAP.org wrote: >Update of /repo/OpenLDAP/pkg/ldap/servers/slapd > >Modified Files: > daemon.c 1.397 -> 1.398 > slap.h 1.796 -> 1.797 > aclparse.c 1.202 -> 1.203 > acl.c 1.318 -> 1.319 > >Log Message: >implement full IPv6 support in ACLs; use URL notation (as suggested by Howard) to disambiguate parsing (ITS#4756) > >CVS Web URLs: > http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/ > http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/daemon.c > http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/slap.h > http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/aclparse.c > http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/acl.c > >Changes are generally available on cvs.openldap.org (and CVSweb) >within 30 minutes of being committed.

1 0

Re: commit: ldap/servers/slapd/overlays accesslog.c
by Howard Chu 16 Dec '06

16 Dec '06

ando(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays > > Modified Files: > accesslog.c 1.67 -> 1.68 > > Log Message: > add support for auditContext (schema differs a bit from <draft-chu-ldap-logschema>, expired) I've made the corresponding change in http://www.highlandsun.com/hyc/drafts/draft-chu-ldap-logschema-xx.html I guess I need to fix up the -ordering- draft so I can get these republished... -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc OpenLDAP Core Team http://www.openldap.org/project/

1 0

auditContext in suffix entry?
by Pierangelo Masarati 16 Dec '06

16 Dec '06

I wonder why the auditContext is not implemented in slapo-accesslog. I needed it in a similar overlay to provide (sort-of-)consumers a means to locate the log db; should I port this fix to slapo-accesslog? p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.n.c. Via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ------------------------------------------ Office: +39.02.23998309 Mobile: +39.333.4963172 Email: pierangelo.masarati(a)sys-net.it ------------------------------------------

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel