Hi,
yes you are right. The rating of the bug is much too high. I didn't test the
ldap-daemon with the default configuration.
I'm just trying to get open exchange server running and configured ldap
according to an howto for sarge found on the net.
/etc/ldap/slapd.conf:
include /etc/ldap/schema/core.schema
include /etc/ldap/schema/cosine.schema
include /etc/ldap/schema/nis.schema
include /etc/ldap/schema/inetorgperson.schema
schemacheck on
pidfile /var/run/slapd/slapd.pid
argsfile /var/run/slapd.args
loglevel 0
modulepath /usr/lib/ldap
moduleload back_bdb
backend bdb
checkpoint 512 30
database bdb
suffix "dc=blahblubb,dc=com"
directory "/var/lib/ldap"
index objectClass eq
lastmod on
access to attrs=userPassword
by dn="cn=admin,dc=blahblubb,dc=com" write
by anonymous auth
by self write
by * none
access to dn.base="" by * read
access to *
by dn="cn=admin,dc=blahblubb,dc=com" write
by * read
include /usr/local/openxchange/share/openxchange.schema
suffix "dc=example,dc=org"
rootdn "cn=Manager,dc=example,dc=org"
rootpw secret
index uid,mailEnabled,cn,sn,givenname,lnetMailAccess,alias,loginDestination
eq,sub
/etc/ldap/ldap.conf:
BASE dc=blahblubb,dc=com
HOST localhost
Cheers, Martin
> There is a point in this report - it seems like an error return is not
> checked here. But the whole problem is easier to find with the
> configuration files.
>
> In this case you seem to have two suffix directives inside a database
> definition which is not supported with the BDB backend and most likely a
> mistake anyway. I can reproduce the problem with about the same trace
> by breaking my config like that.
>
>
> OTOH I don't like people who just dump a lot of less helpful debugging
> output without any description at the maintainer and claim that the
> package is unusable. Immediately segfaults is a bit extreme as the
> default install will not segfault. It would be helpful to describe the
> circumstances.
>
> Please don't just offload your problems on the maintainer without some
> hints.
>
> Thanks
>
> Torsten
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
