[Date Prev][Date Next]
Re: gosa+samba3.schema and slapd.d-configuration-conversion
Christoph Spielmann <email@example.com> writes:
> Hi everybody!
> /usr/lib/openldap/slapd -u ldap -g ldap -f /etc/openldap/slapd.conf -F
> No output on command-line but as i checked the contents of
> /etc/openldap/slapd.d/cn=config i remarked that almost everything was
> missing except the include-ldifs. Next i checked the slapd-logfile and
> this is what has happened:
> So the gosa+samba3.schema seems to make automatic conversion hickup
> somehow. After commenting out the include-line for this schema,
> conversion was successful, so something most be wrong with this
> schema. I tried to figure out what could be wrong with this schema
> myself, but i have no clue where i should start to look. At the moment
> the slave-server is running without the gosa-things included (we don't
> use them yet but sooner or later we'll include gosa) and it's working
> perfectly. But as i need to get gosa working too, i need to know
> what's wrong with the schema. I'll attach the schema to this email,
> hopefully somebody can point me in the right direction.
> # Attributes
> attributetype ( 220.127.116.11.4.1.10098.1.1.12.1 NAME 'gosaSubtreeACL'
> DESC 'GOsa acl entry'
> EQUALITY caseIgnoreMatch
> SUBSTR caseIgnoreSubstringsMatch
> SYNTAX 18.104.22.168.4.1.1422.214.171.124.15)
If this is not a cut and paste error, a white space is missing
following the syntax oid.
Dieter Klünter | Systemberatung
GPG Key ID:8EF7B6C6