> I've tested your latest commit, and most of our tests now run great.
> However, I still get a segault with the two rules below. Please note
> that this segfault only happens when *both* rules are present, each one
> by itself does not cause a segfault :
>
>> access to dn.sub="ou=Affectations,dc=linagora,dc=org"
>> attrs=sigleAbrege,labeledURI,mailRoutingAddress,telephoneNumber,facsimileTelephoneNumber,entry
>> by set="([ldap:///] + (([ldap:///] + ((([ldap:///] + this +
>> [??base?(|(objectClass=affectationLiee)(objectClass=affectationSemiLibre))])/entryDN)/-0)
>> + [??base?])/responsable) +
>> [??base?(|(administrateurResponsable=] + user +
>> [)(administrateur=] + user + [)(membre=] + user + [))])/entryDN"
>> +rscx
>> by * break
>
>> access to dn.sub="ou=Affectations,dc=linagora,dc=org"
>> attrs=domaineMessagerie,finValidite,identifiantHarpegeStructure,responsable,objectClass,entry
>> by set="[ldap:///] + (((([ldap:///] + this +
>> [??base?(|(objectClass=affectationLiee)(objectClass=affectationSemiLibre))])/entryDN)/-100)
>> & ((([ldap:///] + user +
>> [??base?(objectClass=personnel)])/entryDN)/-100)) +
>> [??sub?entryDN=] + user/entryDN" +rscx
>> by * break
>
> I'm afraid that we use quite a few specific schemas so you may not be
> able to reproduce this easily. However, I hope these rules will enable
> you to determine the problematic case. If necessary, I could prepare a
> data and schema extract to reproduce the problem.
That would help, but before you do it, could you please post a backtrace
of the stack when the issue occurs? In case this doesn't suffice, and I
can't figure things out myself, I'll ask you to provide a self-contained
set of data that causes the issue.
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
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
hadmut(a)danisch.de wrote:
> Therefore, slapd should have a client mode where the SyncRepl process is
> performed only on request, but then immediately. There should be an external
> trigger to pull, e.g. send a signal oder do a special LDAP request. slapd should
> then start a SyncRepl.
A simple approach to performing what require is to use back-config to
re-configure syncrepl for the consumer database; this should trigger an
immediate sync. The trigger would then be a LDAPModify replace on the
olcSyncrepl attribute of the database entry.
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
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
raphael.ouazana(a)linagora.com wrote:
> It seems OK with HEAD, but only if I revert this patch:
> http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/sets.c.diff?r1=1.28.…
>
> With this patch, I get a segfault.
I have just committed a cleanup of the slap_set_join() function that
should be consistent. It should fix a leak in case of '&' on
overlapping sets, and consistently handle memory. Can you please test
it and point out failures? If you get any, please post the rules that
cause them, as those I could design worked fine (tested with valgrind).
>
>> And, could you
>> document it on the FAQ, please?
>
> Done: http://www.openldap.org/faq/data/cache/1133.html. Does it seems
> good for you ?
Well, I'd prefer you to merge your comments with the existing, giant
one. The contents look fine (although I'm not a native English
speaker), except for one consideration: for consistency, "/-0" should
return the DN untouched (although useless); perhaps "/-*" or something
like that could be used to explode the DN into all ancestors.
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
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
raphael.ouazana(a)linagora.com wrote:
> Do you think this patch has any chance to be accepted for future 2.4?
Applied (with minor changes) to HEAD, please test. And, could you
document it on the FAQ, please? One improvement that could be applied
is to allow numbers larger than 9...
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
Email: pierangelo.masarati(a)sys-net.it
---------------------------------------
Hi,
I have uploaded a new version of this patch:
ftp://ftp.openldap.org/incoming/raphael-ouazana-070906.patch
Now /-0 allows to get all the parents of an entry. So to keep the example
where user is cn=user,ou=people,dc=example,dc=com:
user/-0 : resolves to set { "cn=user,ou=people,dc=example,dc=com" ,
"ou=people,dc=example,dc=com", "dc=example,dc=com" , "dc=com" , "" }
In fact it was already possible to do that with sets with filters using
entryDN:dnSuperiorMatch, but it was really slower (in 2.3 as in HEAD).
Do you think this patch has any chance to be accepted for future 2.4?
Regards,
Raphael Ouazana.
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. These modifications are not subject to
any
license of Linagora.
The attached modifications to OpenLDAP Software are subject to the following
notice:
Copyright 2007 Raphael Ouazana, Linagora
Redistribution and use in source and binary forms, with or without
modification,
are permitted only as authorized by the OpenLDAP Public License.
On Sep 8, 2007, at 10:02 AM, ando(a)sys-net.it wrote:
> Full_Name: Pierangelo Masarati
> Version: none
> OS: none
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (131.175.154.35)
> Submitted by: ando
>
>
> When hitting "reply" from the ITS, messages are not sent to the
> mailing list,
> even if openldap-its(a)openldap.org is added to the CC field.
Kind of by (broken) design. A reply is intended to be used to send a
note
directly to the submitter. It's broken in that you need to change
the from
header to openldap-its(a)openldap.org for any follow-up to be returned to
openldap-its(a)openldap.org. If you want to reply-all, reply-all to the
copy forwarded to openldap-bugs(a)openldap.org.