ali.pouya(a)free.fr wrote:
> Unfortunately the problem has not been completely fixed in the HEAD.
> With the fix in the head the error message disappears but the contextCSN ins NOT
> ACTUALLY written to the disk. So at the next slapd startup the ContextCSN is
> missing. An the servers hav to resynchronize.
In fact the contextCSN was getting written out, but not getting read back in on
the next startup. This should now be working in HEAD, please test.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
dhawes(a)vt.edu wrote:
> On Thursday 19 July 2007 17:18, ghenry(a)suretecsystems.com wrote:
>> <quote who="dhawes(a)vt.edu">
>>
>>> On Thursday 19 July 2007 05:35, Gavin Henry wrote:
>>>>> An updated version of addpartial is available at:
>>>>>
>>>>> ftp://ftp.openldap.org/incoming/david_hawes-addpartial-070126.tgz
>>>>>
>>>>> This version includes changes to work with OpenLDAP 2.3 as well as
>>>>> ensuring syncrepl works properly.
>>>>>
>>>>> david hawes
>>>> If this hasn't been added to 2.4/HEAD yet, would you consider updating
>>>> it
>>>> for inclusion in 2.4 contrib?
>>> Absolutely, I've been meaning to test with 2.4. I'll bump it to the top
>>> of
>>> the list.
>> Can you make sure that is dynamically configurable via cn=config like
>> everything else in 2.4.
>>
>> Thanks.
>
> I have tested the overlay at
> ftp://ftp.openldap.org/incoming/david_hawes-addpartial-070126.tgz, and it
> works with 2.4.4alpha, including dynamic loading via cn=config.
>
> Apart from using "overlay addpartial", there is no slapd configuration for
> addpartial. I believe this means it doesn't need its own schema to work
> correctly. Please correct me if I am wrong about this.
That's correct. If there was no config needed under the old mechanism, then
none is needed with the new either.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
On Thursday 19 July 2007 17:18, ghenry(a)suretecsystems.com wrote:
> <quote who="dhawes(a)vt.edu">
>
> > On Thursday 19 July 2007 05:35, Gavin Henry wrote:
> >> > An updated version of addpartial is available at:
> >> >
> >> > ftp://ftp.openldap.org/incoming/david_hawes-addpartial-070126.tgz
> >> >
> >> > This version includes changes to work with OpenLDAP 2.3 as well as
> >> > ensuring syncrepl works properly.
> >> >
> >> > david hawes
> >>
> >> If this hasn't been added to 2.4/HEAD yet, would you consider updating
> >> it
> >> for inclusion in 2.4 contrib?
> >
> > Absolutely, I've been meaning to test with 2.4. I'll bump it to the top
> > of
> > the list.
>
> Can you make sure that is dynamically configurable via cn=config like
> everything else in 2.4.
>
> Thanks.
I have tested the overlay at
ftp://ftp.openldap.org/incoming/david_hawes-addpartial-070126.tgz, and it
works with 2.4.4alpha, including dynamic loading via cn=config.
Apart from using "overlay addpartial", there is no slapd configuration for
addpartial. I believe this means it doesn't need its own schema to work
correctly. Please correct me if I am wrong about this.
Thanks,
dave
On Jul 20, 2007, at 3:31 PM, Howard Chu wrote:
> pturgyan(a)umich.edu wrote:
>> Full_Name: Paul Turgyan
>> Version: 2.3.35
>> OS: linux 2..6.18 from source URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (141.213.231.171)
>> When calling ldap_add_result_entry with an empty list or when
>> starting a new
>> list, ldap_add_result_entry crashes
>> with a SEGFAULT at line 67.
>> Here is a patch:
>
> A different fix is now in HEAD, please test.
>
> --
> -- Howard Chu
> Chief Architect, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/
Works for me! Thanks.
pturgyan(a)umich.edu wrote:
> Full_Name: Paul Turgyan
> Version: 2.3.35
> OS: linux 2..6.18 from source
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (141.213.231.171)
>
>
> When calling ldap_add_result_entry with an empty list or when starting a new
> list, ldap_add_result_entry crashes
> with a SEGFAULT at line 67.
>
> Here is a patch:
A different fix is now in HEAD, please test.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Paul Turgyan
Version: 2.3.35
OS: linux 2..6.18 from source
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (141.213.231.171)
When calling ldap_add_result_entry with an empty list or when starting a new
list, ldap_add_result_entry crashes
with a SEGFAULT at line 67.
Here is a patch:
*** addentry.c Tue Jan 2 16:43:48 2007
--- addentry.c+ Fri Jul 20 13:48:41 2007
***************
*** 64,69 ****
--- 64,72 ----
assert( e != NULL );
e->lm_chain = *list;
+ if (*list)
e->lm_chain_tail = (*list)->lm_chain_tail;
+ else
+ e->lm_chain_tail = NULL;
*list = e;
}
<quote who="hyc(a)symas.com">
> ghenry(a)OpenLDAP.org wrote:
>> Full_Name: Gavin Henry
>> Version: HEAD
>> OS:
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (80.229.93.1)
>> Submitted by: ghenry
>>
>>
>> Dear All,
>>
>> It's not clear or explained what AVA means in slapd-meta(5) and
>> slapo-rwm(5)
>
> Standard terminology in X.500/LDAP. "Attribute Value Assertion"
>>
>> A user was asking in #ldap
>>
>> I presume it means "Attribute Value"?
>>
>> If so, I will add an explaination in each man page.
>
> OpenLDAP docs are not intended to explain the basics of LDAP. You're
> expected
> to already know LDAP or refer to the RFCs for basic terminology.
Closing ITS.
>
> --
> -- Howard Chu
> Chief Architect, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/
>
>
>
quanah(a)zimbra.com wrote:
> Full_Name: Quanah Gibson-Mount
> Version: 2.3.34
> OS: NA
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (71.202.148.128)
>
>
> If a database has a zero-length suffix, the NULL context entry gets an entry ID
> of zero, which is usually an invalid ID number and always omitted from indexing.
> But it looks like with slapadd -q, it is possible for this entry to get
> included in various indices, which will totally confuse them.
>
> (per Howard)
I actually filed this already instead of waiting for you (ITS#5052). A patch is
already in HEAD for testing. This ITS will be closed.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
ghenry(a)OpenLDAP.org wrote:
> Full_Name: Gavin Henry
> Version: HEAD
> OS:
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (80.229.93.1)
> Submitted by: ghenry
>
>
> Dear All,
>
> It's not clear or explained what AVA means in slapd-meta(5) and slapo-rwm(5)
Standard terminology in X.500/LDAP. "Attribute Value Assertion"
>
> A user was asking in #ldap
>
> I presume it means "Attribute Value"?
>
> If so, I will add an explaination in each man page.
OpenLDAP docs are not intended to explain the basics of LDAP. You're expected
to already know LDAP or refer to the RFCs for basic terminology.
--
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Quanah Gibson-Mount
Version: 2.3.34
OS: NA
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (71.202.148.128)
If a database has a zero-length suffix, the NULL context entry gets an entry ID
of zero, which is usually an invalid ID number and always omitted from indexing.
But it looks like with slapadd -q, it is possible for this entry to get
included in various indices, which will totally confuse them.
(per Howard)
--Quanah