[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#3901) slapd segmentation fault if directive starts with whitespace

[I suspect this was meant for the ITS as well]

> Pierangelo Masarati wrote:
>> I've played a bit with other standard directives and no more SIGSEGVs were
>> noticed.  Can you please test the fixes?
> Where would I find them? CVS?

yes; for RE22:

cvs diff -u -r -r servers/slapd/back-bdb/init.c

> I just ran into another problem. I tried to build a syncrep provider,
database description:
> database        	bdb
> suffix          	"dc=rackland,dc=de"
> rootdn			"dc=rackland,dc=de"
> rootpw			"..."
> directory       	"/var/lib/ldap/rackland"
> index           	objectClass eq cn uid email racklandResponsible lastmod
> overlay 		syncprov
> access to attrs=userPassword
>        	by dn="cn=admin,dc=rackland,dc=de" write
>        	by self write
> 	by dnattr=owner write
> 	by dn="cn=imap@sklave9.rackland.de,ou=services,dc=rackland,dc=de" read
>        	by anonymous auth
>        	by * none
> access to dn.base=""
> 	by * read
> access to *
>        	by dn="cn=admin,dc=rackland,dc=de" write
>        	by * read
> Without the overlay statement everything works well. But with the
statement I get the error message
> line 8: extra junk after "index <attr> [pres,eq,approx,sub]" line (ignored)

The "index" directive above is incorrect; see slapd.conf(5) (or the error
message above) for the correct syntax.  The message should appear
regardless of having an "overlay" directive; I note, however, that the
syncprov overlay cannot be used with 2.2.

> when starting the slapd. I guess there is another problem with
> parameter parsing. If not, how would I configure a syncrep
> provider?

Syncrep providers don't need to be configured at all.  In any case,
further issues should be discussed on the mailing list, as they do not
appear to be related to this ITS.


Pierangelo Masarati

    SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497