openldap-bugs

openldap-bugs@openldap.org

1 participants
21065 discussions

Re: slapo-unique man page misleading (ITS#5908)
by quanah＠zimbra.com 30 Jan '09

30 Jan '09

--On Friday, January 30, 2009 7:08 PM +0000 Gavin Henry <ghenry(a)suretecsystems.com> wrote: > Ok, so this should be in the man page. Where else should this be listed > that affects other overlays? Eh, I'm not sure it should be in the man page. The point is, if you ever want guaranteed atomic writes, you have to use slapo-accesslog to serialize them. That's an issue that affects other LDAP servers as well. AS Pierangelo said: There is no guarantee of DSA-wide or even database-wide atomicity in write operations, including internal ones. This was never even intended to be in place. This is a known design limitation not only of slapo-unique, but also of slapd (and, I'd say, of LDAP itself). --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: slapo-unique man page misleading (ITS#5908)
by ghenry＠suretecsystems.com 30 Jan '09

30 Jan '09

Ok, so this should be in the man page. Where else should this be listed that affects other overlays? ------Original Message------ From: Quanah Gibson-Mount Sender: To: Gavin Henry To: openldap-its(a)openldap.org Subject: Re: slapo-unique man page misleading (ITS#5908) Sent: 30 Jan 2009 19:04 --On Thursday, January 29, 2009 3:48 PM +0000 ghenry(a)suretecsystems.com wrote: >> Huh? slapo-unique only does internal searches. The writes are all user >> ops, >> and accesslog will serialize all of them. > > So, where does this leave us? If you want guaranteed atomic writes, use slapo-accesslog on your master to serialize them. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration -- 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/ Suretec Systems is a limited company registered in Scotland. Registered number: SC258005. Registered office: 13 Whiteley Well Place, Inverurie, Aberdeenshire, AB51 4FP. Subject to disclaimer at http://www.suretecgroup.com/disclaimer.html

1 0

Re: slapo-unique man page misleading (ITS#5908)
by quanah＠zimbra.com 30 Jan '09

30 Jan '09

--On Thursday, January 29, 2009 3:48 PM +0000 ghenry(a)suretecsystems.com wrote: >> Huh? slapo-unique only does internal searches. The writes are all user >> ops, >> and accesslog will serialize all of them. > > So, where does this leave us? If you want guaranteed atomic writes, use slapo-accesslog on your master to serialize them. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5898) test044 abort with back-ldif
by ando＠sys-net.it 30 Jan '09

30 Jan '09

Hallvard B Furuseth wrote: > Pierangelo Masarati writes: >> I don't know how useful it would be to have back-ldif directly implement >> compare, as soon as one only uses it for back-config and not for a real >> storage with stacked overlays (however I note that back-config needs at >> least to nicely interoperate with one overlay: slapo-syncprov). > > Syncprov does use compare, and back-config doesn't provide it. > I don't know if that's a problem. In any case, the fallthru compare works fine, except for those cases that require overlay manipulation of the call before actually comparing data. This is what happens to slapo-dynlist: compare gets straight to back-ldif without prior generating the dynamic listing. > I forgot, back-config doesn't fall back to back-ldif for reads. > So I guess it's just as well to leave back-ldif as it is. :) 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#5898) test044 abort with back-ldif
by h.b.furuseth＠usit.uio.no 30 Jan '09

30 Jan '09

Pierangelo Masarati writes: > I don't know how useful it would be to have back-ldif directly implement > compare, as soon as one only uses it for back-config and not for a real > storage with stacked overlays (however I note that back-config needs at > least to nicely interoperate with one overlay: slapo-syncprov). Syncprov does use compare, and back-config doesn't provide it. I don't know if that's a problem. I forgot, back-config doesn't fall back to back-ldif for reads. So I guess it's just as well to leave back-ldif as it is. -- Hallvard

1 0

Re: (ITS#5898) test044 abort with back-ldif
by ando＠sys-net.it 30 Jan '09

30 Jan '09

h.b.furuseth(a)usit.uio.no wrote: > Pierangelo Masarati writes: >> Probably related; in any case, misused in slapo-dynlist(5). Now slapd >> doesn't assert() any more. However, the test fails because back-ldif >> does not implement compare, and falls back to be_fetch(), which does not >> trigger dynlist expansion. > > Yes, the "compare without help from the backend" functionality has been > broken for years - which I presume means it's hard to fix, or needs a > different design. > > Should we patch it over by adding Compare to back-ldif and whatever else > lacks it? Or is this a "fix coming Real Soon Now" issue so it's good > to have this reminder from a backend which doesn't provide Compare? Not sure whether it's about to come sooner or later, but the issue is always about be_fetch, aka bi_entry_get_rw() whose design Is Broken (TM) (actually, it broke when overlays came into play). I don't know how useful it would be to have back-ldif directly implement compare, as soon as one only uses it for back-config and not for a real storage with stacked overlays (however I note that back-config needs at least to nicely interoperate with one overlay: slapo-syncprov). 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#5898) test044 abort with back-ldif
by h.b.furuseth＠usit.uio.no 30 Jan '09

30 Jan '09

Pierangelo Masarati writes: > Probably related; in any case, misused in slapo-dynlist(5). Now slapd > doesn't assert() any more. However, the test fails because back-ldif > does not implement compare, and falls back to be_fetch(), which does not > trigger dynlist expansion. Yes, the "compare without help from the backend" functionality has been broken for years - which I presume means it's hard to fix, or needs a different design. Should we patch it over by adding Compare to back-ldif and whatever else lacks it? Or is this a "fix coming Real Soon Now" issue so it's good to have this reminder from a backend which doesn't provide Compare? -- Hallvard

1 0

Re: (ITS#5915) Some man pages still only talk about slapd.conf
by h.b.furuseth＠usit.uio.no 30 Jan '09

30 Jan '09

hyc(a)symas.com writes: > I guess for this release (and probably for 2.5) we're just going to > have to document both, as cumbersome as that will be. When we get to > to 2.6/3.0 and drop support for slapd.conf we'll have to come back > thru again and delete the slapd.conf references from all the > docs. Unless anyone has a better idea... I'm not sure I see the problem, except that Someone(TM) must do the work... For each configuration keyword, use two headers in the manpages: Both the slapd.conf syntax and the cn=config syntax. Explain at the beginning of slapd.conf.5 or slapd-config.5. We'll be deleting most of the other one, since they are mostly duplicates. Other manpages need just one-line reminder for explanation. There'll be exceptions that spell things out too differently, or use slightly different parameters in slapd.conf and cn=config. Keep them in just slapd.conf-syntax, and add a separate cn=config attribute description below. Likely that'll only need to explain the difference. Don't go trough literary contortions to fit them both into the same description. Some of these will likely be things that could use some cleanup in the code anyway, bringing the two config formats in sync. Take a random sample of the slapd.conf-syntax example sections and replace with their cn=config equivalent. Ensure all example sections say either "slapd.conf example" or "cn=config example". slapd.conf.5 and slapd-config.5 themselves will need sections about how they work as interfaces to configuration, separate from the configuration keywords/attributes themselves. Since we are moving towards cn=config, I suppose it's that one which should keep the actual keyword/attribute descriptions. Or they could move to a third file. -- Hallvard

1 0

Re: (ITS#5898) test044 abort with back-ldif
by ando＠sys-net.it 30 Jan '09

30 Jan '09

h.b.furuseth(a)usit.uio.no wrote: >> When using the back-ldif backend with test044, it aborts: > > Probably ITS#5340. Probably related; in any case, misused in slapo-dynlist(5). Now slapd doesn't assert() any more. However, the test fails because back-ldif does not implement compare, and falls back to be_fetch(), which does not trigger dynlist expansion. 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#5913) supportedSASLMechanisms EXTERNAL not Work
by ando＠sys-net.it 29 Jan '09

29 Jan '09

jarbas.peixoto(a)gmail.com wrote: > Full_Name: Jarbas Peixoto Junior > Version: 2.4.11 > OS: Debian Lenny > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (200.152.43.195) > > > I have two servers: > > * Server A: Debian Etch - Works Fine > > * Server B: Debian Lenny - Do not Works supportedSASLMechanisms EXTERNAL > > In Server A I have: > > # ldapsearch -v -H ldap://server-Etch -b "" -LLL -s base supportedSASLMechanisms > -ZZ > ldap_initialize( ldap://server-Etch ) > SASL/EXTERNAL authentication started > SASL username: emailAddress=jarbas.peixoto(a)previdencia.gov.br,CN=jarbas.peixoto,OU=DATAPREV,O=Previdencia > Social,L=Campo Grande,ST=Mato Grosso do Sul,C=BR > SASL SSF: 0 > filter: (objectclass=*) > requesting: supportedSASLMechanisms > dn: > supportedSASLMechanisms: PLAIN > supportedSASLMechanisms: DIGEST-MD5 > supportedSASLMechanisms: LOGIN > supportedSASLMechanisms: NTLM > supportedSASLMechanisms: CRAM-MD5 > supportedSASLMechanisms: EXTERNAL > > In Server B I have: > > # ldapsearch -v -H ldap://server-Lenny -b "" -LLL -s base > supportedSASLMechanisms -ZZ > ldap_initialize( ldap://server-Lenny:389/??base ) > ldap_start_tls: Connect error (-11 ^^^ start TLS is failing. There is no evidence of a bug in the software; likely either the client or the server's TLS is misconfigured. Please direct software usage questions to the openldap-software list. 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

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