openldap-bugs July 2009

openldap-bugs@openldap.org

49 participants
166 discussions

RE: (ITS#6201) Double free in syncprov
by quanah＠zimbra.com 09 Jul '09

09 Jul '09

--On Thursday, July 09, 2009 10:18 AM +0000 Alister.Winfield(a)sns.bskyb.com wrote: > I think I have it (bad configuration)... > > Okay so it might be a configuration 'error' but I guess its worth trying > to= avoid the crash. Hi Alister, Can you provide an example of your misconfigured slapd for ease of debugging? Obviously, this is non-critical but I agree it would be nice to make sure this sort of configuration error is caught more gracefully. Thanks, Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#6207) Build farm
by ghenry＠OpenLDAP.org 09 Jul '09

09 Jul '09

Full_Name: Gavin Henry Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Submitted by: ghenry Build farm should be complete by now.

1 0

(ITS#6206) Admin guide appendices or tools in contrib should be better than Ubuntu docs
by ghenry＠OpenLDAP.org 09 Jul '09

09 Jul '09

Full_Name: Gavin Henry Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Submitted by: ghenry Must beat or match: https://help.ubuntu.com/9.04/serverguide/C/openldap-server.html

1 0

(ITS#6205) Discuss slapadd -S in Admin guide appendix
by ghenry＠OpenLDAP.org 09 Jul '09

09 Jul '09

Full_Name: Gavin Henry Version: OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Submitted by: ghenry As per http://www.openldap.org/lists/openldap-bugs/200809/msg00140.html

1 0

(ITS#6204) General upgrade procedure missing from Admin guide
by ghenry＠OpenLDAP.org 09 Jul '09

09 Jul '09

Full_Name: Gavin Henry Version: HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Submitted by: ghenry Documenting this procedure should be in the Admin Guide like http://www.openldap.org/faq/index.cgi?file=842 Gavin.

1 0

Re: (ITS#6202) adding command line option to disable line breaking in ldif output
by dieter＠bloms.de 09 Jul '09

09 Jul '09

Hi, On Thu, Jul 09, Michael Str=F6der wrote: > > I want to do an enhancement request for ldapsearch, because it insert a= line > > break after 78 characters. > > Many people like me use the ldapsearch command in shell script and have= to > > workaround this issue. > > Maybe it make sense to add a command line option to deactivate this lin= e breaks. >=20 > I'd rather recommend to use a decent scripting language with LDAP and/or > LDIF modules than using ldapsearch in shell scripts. This gives better > control over data and error handling. there are several ldapsearch binaries from other distributor, which includes an option -T for this concern. http://www.koders.com/c/fidD1B671B4DA7CB116CA077E4694EEBAE167D3F85E.aspx http://docs.sun.com/source/816-6400-10/lsearch.html =2E.. so why doesn't ldapsearch from openldap inlcude this option. It doesn't break any rfc and historcal implementation and as far as I can see (with google), there are many admins who have to workaround this with a little perl script. I think it must be a little diff, with a few lines I can write it, but is someone willing to inlcude it in the upstream versions ? --=20 Gru=DF Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the =46rom field.

1 0

Re: (ITS#6202) adding command line option to disable line breaking in ldif output
by michael＠stroeder.com 09 Jul '09

09 Jul '09

openldap.org(a)bloms.de wrote: > Full_Name: Dieter Bloms > Version: all > OS: linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (193.27.50.90) > > > I want to do an enhancement request for ldapsearch, because it insert a line > break after 78 characters. > Many people like me use the ldapsearch command in shell script and have to > workaround this issue. > Maybe it make sense to add a command line option to deactivate this line breaks. I'd rather recommend to use a decent scripting language with LDAP and/or LDIF modules than using ldapsearch in shell scripts. This gives better control over data and error handling. Ciao, Michael.

1 0

(ITS#6203)
by Andrew.Morgan＠Sun.COM 09 Jul '09

09 Jul '09

wait_until_ready is documented here: http://dev.mysql.com/doc/ndbapi/en/class-ndb-cluster-connection-methods.html #class-ndb-cluster-connection-wait-until-ready -----Original Message----- From: openldap-its(a)OpenLDAP.org [mailto:openldap-its@OpenLDAP.org] Sent: 09 July 2009 14:51 To: Andrew.Morgan(a)Sun.COM Subject: Re: (ITS#6203) Problem & solution for back-ndb issue connecting to Cluster data nodes *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** Thanks for your report to the OpenLDAP Issue Tracking System. Your report has been assigned the tracking number ITS#6203. One of our support engineers will look at your report in due course. Note that this may take some time because our support engineers are volunteers. They only work on OpenLDAP when they have spare time. If you need to provide additional information in regards to your issue report, you may do so by replying to this message. Note that any mail sent to openldap-its(a)openldap.org with (ITS#6203) in the subject will automatically be attached to the issue report. mailto:openldap-its@openldap.org?subject=(ITS#6203) You may follow the progress of this report by loading the following URL in a web browser: http://www.OpenLDAP.org/its/index.cgi?findid=6203 Please remember to retain your issue tracking number (ITS#6203) on any further messages you send to us regarding this report. If you don't then you'll just waste our time and yours because we won't be able to properly track the report. Please note that the Issue Tracking System is not intended to be used to seek help in the proper use of OpenLDAP Software. Such requests will be closed. OpenLDAP Software is user supported. http://www.OpenLDAP.org/support/ -------------- Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved.

1 0

(ITS#6203) Problem & solution for back-ndb issue connecting to Cluster data nodes
by andrew.morgan＠sun.com 09 Jul '09

09 Jul '09

Full_Name: Andrew Morgan Version: 2.4.16 OS: Ubuntu URL: Submission from: (NULL) (90.193.196.76) I am running MySQL Cluster with data nodes all running on the same host. I configured, built and installed OpenLDAP with back-ndb but when I run "slapd -d 5", it failed with "ndb_db_open: ni_cluster[0]->wait failed (1)". Looking at the code in "back-ndb/init.cpp" this implies that it was able to connect to the Cluster management node but only the first of the data nodes. The cause of this is line 133: "ni->ni_cluster[i]->wait_until_ready( 30, 0 );" - the 30,0 means wait up to 30 seconds for first data node but then no time at all for the others; the fact that the method returned 1 means that the first node was found to be live. The second parameter should be set to a non-zero value to give the other data nodes chance to show as being live. I changed the 0 to 30, recompiled/installed and slapd came up correctly.

1 0

Re: (ITS#6139) slapd: password-hash rejects multiple values
by h.b.furuseth＠usit.uio.no 09 Jul '09

09 Jul '09

It has been fixed in CVS (and in next OpenLDAP release): http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/bconfig.c.diff?r1=1.… -- Hallvard

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs July 2009