openldap-bugs

openldap-bugs@openldap.org

1 participants
20959 discussions

RE: (ITS#5919) URI syntaxe (ldap:///dc=my%2cdc=domaine)
by philippe.eychart＠informatique.gov.pf 27 Mar '09

27 Mar '09

Hi, So, no idea about how to save the result of a previous SRV request in the implementation of the weight notion according to the rfc 2782?... >From my part either :-( (perhaps, somewhere in the kernel?...) PE PS: About the patch, I use it for several weeks now and everything seems good : no bugg, functioning and result waited ;-)

1 0

Re: (ITS#6038) Write slapadd progress meter to stdout
by hyc＠symas.com 27 Mar '09

27 Mar '09

Hallvard B Furuseth wrote: > hyc(a)symas.com writes: >> Just redirect stdin, and the meter will automatically turn itself off. > > It was stderr, not stdin - which after all can be the ldif. > Stdout is better. > No, you misunderstand. Redirecting stderr (or stdout) merely sends the progress info to that destination. Piping input on stdin will turn it off, so there's no progress info to redirect. Writing progress to stderr is the correct thing to do, because it's transient info that isn't meant to be saved. Checking whether stdout is redirected or not is fine, but writing progress info to stdout is not. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#6038) Write slapadd progress meter to stdout
by h.b.furuseth＠usit.uio.no 26 Mar '09

26 Mar '09

hyc(a)symas.com writes: > Just redirect stdin, and the meter will automatically turn itself off. It was stderr, not stdin - which after all can be the ldif. Stdout is better. -- Hallvard

1 0

Re: (ITS#6038) Write slapadd progress meter to stdout
by hyc＠symas.com 26 Mar '09

26 Mar '09

rein(a)OpenLDAP.org wrote: > Full_Name: Rein Tollevik > Version: CVS HEAD > OS: Irrelevant > URL: > Submission from: (NULL) (84.215.36.97) > Submitted by: rein > > > The slapadd progress meter is written to stderr, and the only way to get rid of > it is currently to redirect stderr. I don't want the meter in my small test > scripts, as it is not very useful on minimal input and clutters the test output. > It should be possible to disable the meter without loosing all error messages, > a fix that writes the meter to stdout instead is coming. > > Options to enable/disable the meter would be nice, but the obvious candidates -q > and -v are both occupied... Just redirect stdin, and the meter will automatically turn itself off. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

(ITS#6038) Write slapadd progress meter to stdout
by rein＠OpenLDAP.org 26 Mar '09

26 Mar '09

Full_Name: Rein Tollevik Version: CVS HEAD OS: Irrelevant URL: Submission from: (NULL) (84.215.36.97) Submitted by: rein The slapadd progress meter is written to stderr, and the only way to get rid of it is currently to redirect stderr. I don't want the meter in my small test scripts, as it is not very useful on minimal input and clutters the test output. It should be possible to disable the meter without loosing all error messages, a fix that writes the meter to stdout instead is coming. Options to enable/disable the meter would be nice, but the obvious candidates -q and -v are both occupied... Rein Tollevik Basefarm AS

1 0

(ITS#6037) errno in signal handlers
by h.b.furuseth＠usit.uio.no 26 Mar '09

26 Mar '09

Full_Name: Hallvard B Furuseth Version: HEAD, RE24 OS: URL: Submission from: (NULL) (129.240.6.233) Submitted by: hallvard Signal handlers slapd/daemon.c:slap_sig_shutdown()/slap_sig_wake() need to save/restore errno, since they call functions that can modify errno. And/or possibly they need sock_errno() - sock_errset() from ac/socket.h, since they use tcp_write()? I don't know if that's safe inside signal handlers, or if Windows itself saves/restores this code around signal handlers. slapd/main.c:wait4child() can loop forever after EINTR, since it checks for errno even when the waitpid returns 0. I don't know if there is a good reason it does that. Some of the commits have my name on them but I think I copied it from elsewhere. Anyway, I'm doing the minimal changes now: save/restore errno, and set errno=0 in each loop iteration instead of before the loop. Anyone with better ideas can take it from there.

1 0

Re: (ITS#6035) slapd requires restart after modifying olcAuthzRegexp
by ando＠sys-net.it 26 Mar '09

26 Mar '09

quanah(a)zimbra.com wrote: > --On Thursday, March 26, 2009 4:14 PM +0000 hyc(a)symas.com wrote: > >> This is a known limitation in authz regexp support. There are no plans >> to change this any time soon. > > Where's this limitation documented? What other parameters in the config > backend have the same flaw? We've certainly fixed this for a number of > other things. Indeed, it has been finally, although rather inelegantly, fixed in slapo-rwm(5), AFAIR. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

Re: (ITS#6035) slapd requires restart after modifying olcAuthzRegexp
by quanah＠zimbra.com 26 Mar '09

26 Mar '09

--On Thursday, March 26, 2009 4:14 PM +0000 hyc(a)symas.com wrote: > This is a known limitation in authz regexp support. There are no plans > to change this any time soon. Where's this limitation documented? What other parameters in the config backend have the same flaw? We've certainly fixed this for a number of other things. I don't even see authz-regexp/olcAuthzRegexp mentioned in chapters 5 or 6 in the admin guide, and the man pages don't note this limitation. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#6035) slapd requires restart after modifying olcAuthzRegexp
by hyc＠symas.com 26 Mar '09

26 Mar '09

This is a known limitation in authz regexp support. There are no plans to change this any time soon. On Thu, Mar 26, 2009 at 03:33:37AM +0000, dgbaley27(a)verizon.net wrote: > Full_Name: Matthew Monaco > Version: 2.4.11 > OS: GNU/Linux 2.6.27-7 (Ubuntu 8.10 Server JeOS) > URL: > Submission from: (NULL) (96.242.209.249) > > > After modifying existing olcAuthzRegexp and/or adding/removing additional > olcAuthzRegexp from cn=config, I needed to restart slapd for the changes to take > effect. > > I'm not sure if it matters but I was using ldapvi to do the modification. > > I can however, confirm that the changes immediately appeared in various other > ldap browsers (such as Apache Directory Studio).

1 0

(ITS#6036) Crash: UUIDNormalize doesn't clear output on error
by test.007＠seznam.cz 26 Mar '09

26 Mar '09

Full_Name: Test Seven Version: 2.4.15 OS: Windows URL: Submission from: (NULL) (195.39.55.20) --- schema_init.orig 2009-01-22 01:01:03.000000000 +0100 +++ schema_init.c 2009-03-26 15:12:15.578125000 +0100 @@ -2814,6 +2814,7 @@ UUIDNormalize( } else { slap_sl_free( normalized->bv_val, ctx ); + BER_BVZERO(normalized); return LDAP_INVALID_SYNTAX; } I encountered a crash in str2entry2() final cleanup. It turned out that it called ordered_value_normalize(), which called UUIDNormalize(), which left the value nonzero but already free-d.

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