openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

Re: (ITS#6725) How to install multiple instances of openldap on different port(389, 390 391)
by rein＠OpenLDAP.org 26 Nov '10

26 Nov '10

On 11/25/10 17:27 , devman1624(a)yahoo.com wrote: > Can some one tell me how to install multiple instances of openldap on different > port(i.e on 389, 390 391). > > Accroding to me there is only one option, that is multiple installation od > openldap. Please direct usage questions to the openldap-technical list, the ITS system is for bugs. And please RTFM before doing so, the answer to your question is clearly stated there. Rein

1 0

(ITS#6726) How to install multiple instances of openldap on different port(389, 390 391)
by devman1624＠yahoo.com 25 Nov '10

25 Nov '10

Full_Name: DevMan Version: 2.4.16 OS: RHEL54. URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (122.177.216.157) Hi All, Can some one tell me how to install multiple instances of openldap on different port(i.e on 389, 390 391). Accroding to me there is only one option, that is multiple installation od openldap. Thx DevMan

1 0

(ITS#6725) How to install multiple instances of openldap on different port(389, 390 391)
by devman1624＠yahoo.com 25 Nov '10

25 Nov '10

1 0

Re: (ITS#6686) VLV overlay fails to handle multiple search operations per LDAP connection
by raphael.ouazana＠linagora.com 25 Nov '10

25 Nov '10

Hi, Here is a new version of the patch: ftp://ftp.openldap.org/incoming/raphael-ouazana-101125-sssvlv-multiple-requ… It fixes some segfaults that the previous patch introduced if you use pagedResults or sss instead of VLV. It also fixes a segfault in the original sssvlv code when making two successive requests on the same connexion (can be triggered by ldapsearch). Finally here is an update of the copyright notice too: Legal notice: This patch file is derived from OpenLDAP Software. All of the modifications to OpenLDAP Software represented in this following patch were developed by Raphael Ouazana raphael.ouazana(a)linagora.com and Sebastien Bahloul sbahloul(a)linagora.com. These modifications are not subject to any license of Linagora. The attached modifications to OpenLDAP Software are subject to the following notice: Copyright 2010 Raphael Ouazana, Linagora Copyright 2010 Sebastien Bahloul, Linagora Redistribution and use in source and binary forms, with or without modification, are permitted only as authorized by the OpenLDAP Public License. Regards, Raphaël Ouazana

1 0

Re: (ITS#6720) back-ldap core dump
by masarati＠aero.polimi.it 24 Nov '10

24 Nov '10

olivier.chirossel(a)sfr.com wrote: > I have to migrate from a openldap 2.3.x to openldap 2.4. During this migration > phase i want my openldap 2.3.x master replicate with slurpd to my new openldap > 2.4.x master mirror mode architecture with some rewriting rules for split my big > directory. > > > I configure a proxy ldap using back-ldap with slapo-rwm overlay, but > operational attributes related to entry creation and modification are > proxied, even when i put « lastmod off » in the conf, contrary of the man of > slapd-ldap > > > > So i put rw-map directives in the conf for strip operationnal attributes but > this kind of operation generate a core dump Your configuration contains a load of custom schema items; can you create a simple configuration, based on standard attributes, that reproduces the problem (I mean: the sigsegv), and describe which operation is causing it? Is it a client operation or replication? In your report you mention the intention to use "master mirror mode" (?), it's not clear what back-ldap has to do with it. p.

1 0

Re: (ITS#6603) EAGAIN, EWOULDBLOCK occasionally used without checking #ifdef
by h.b.furuseth＠usit.uio.no 24 Nov '10

24 Nov '10

> Here's a patch, please inspect. > > <ftp://ftp.openldap.org/incoming/pierangelo.masarati.2010-11-23.1.patch> Looks fine to me. -- Hallvard

1 0

Re: (ITS#6532) Support for common orderingMatching rules in extensible match filters
by h.b.furuseth＠usit.uio.no 24 Nov '10

24 Nov '10

Variant applied to HEAD: schema_init.c 1.473. Correct 'match' code is simpler than yours, now that you've pointed me in the right direction. All ordering rules except CSNOrderingMatch and UUIDOrderingMatch now support extensible match. Someone who knows slapd's use of CSNs and UUIDs can (tell me to) do the same there if it's OK to do so. I didn't want to meddle carelessly, also I don't know what UUIDOrderingMatch's SLAP_MR_MUTATION_NORMALIZER flag means and if it would interfere. -- Hallvard

1 0

Re: (ITS#6603) EAGAIN, EWOULDBLOCK occasionally used without checking #ifdef
by masarati＠aero.polimi.it 23 Nov '10

23 Nov '10

>> At least in libldap and liblber EAGAIN and EWOULDBLOCK are >> occasionally used without checking whether they are defined or not. >> Either the checks should be removed, counting on the fact that these >> error codes are always defined, or they should be used consistently. > > I'd say the libldap #ifdefs can safely be removed by now: "cvs annotate" > says os-ip.c has had unconditional EWOULDBLOCK since rev 1.34 (Aug > 1999), and request.c unconditional EAGAIN since rev 1.85 (Aug 2002). > No bug reports since then... > > We need to keep the '#if EWOULDBLOCK != EAGAIN's in switches, though. > > liblber always #ifdefs them, except in a test program. I suppose these > #ifdefs could stay in case someone uses the liblber source stand-alone. Here's a patch, please inspect. <ftp://ftp.openldap.org/incoming/pierangelo.masarati.2010-11-23.1.patch> p.

1 0

(ITS#6724) Feature request: support for PKCS11 pin input callback in public TLS api
by silvan＠kernelconcepts.de 23 Nov '10

23 Nov '10

Full_Name: Silvan Marco Fin Version: OS: Ubuntu Linux 10.04 URL: Submission from: (NULL) (217.146.132.69) Support for PKCS #11 devices in TLS via MozNSS in OpenLDAP currently lacks the possibility to "ask" for a PIN via callback. The methods supplied in tls_m.c are reading a PIN from a file or alternativly reading a PIN from STDIN. To add the needed flexibility to the MozNSS part, an additional callback argument to the init function or alternatively an additional set function for the callback would be needed. http://www.mozilla.org/projects/security/pki/nss/ref/ssl/pkfnc.html#1023128 provides the signature for the callback function. Since GnuTLS and OpenSSL provide PKCS #11 support by themselves in some way, I propose to add an additional set function to OpenLDAPs public TLS API to register a callback with the corresponding security library.

1 0

Re: (ITS#5421) slapd vs LDAP_R_COMPILE
by h.b.furuseth＠usit.uio.no 23 Nov '10

23 Nov '10

Taken to this thread: http://www.openldap.org/lists/openldap-devel/201011/msg00013.html librewrite & co vs. logging & ldap-int.h Since this ITS now depends on the ldap_debug hack in ldap_log.h, I'm removing some unnecessary '#include <ldap_log.h>'s for clarity. -- Hallvard

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs