Hello Aaron,
I'm not add ou modify nothing in samba.schema.
But when i open samba.schehema I see:
#attributetype ( 1.3.6.1.4.1.7165.2.1.1 NAME 'lmPassword'
# DESC 'LanManager Passwd'
# EQUALITY caseIgnoreIA5Match
# SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{32} SINGLE-VALUE )
#attributetype ( 1.3.6.1.4.1.7165.2.1.2 NAME 'ntPassword'
# DESC 'NT Passwd'
# EQUALITY caseIgnoreIA5Match
# SYNTAX 1.3.6.1.4.1.1466.115.121.1.26{32} SINGLE-VALUE )
If I Can uncomment this lines ?
in java.scheme all lines is not uncomment.
attributetype ( 1.3.6.1.4.1.42.2.27.4.1.6
NAME 'javaClassName'
DESC 'Fully qualified name of distinguished Java class or interface'
EQUALITY caseExactMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE )
Rodrigo Faria Tavares
________________________________
De: Aaron Richton <[email protected]>
Para: rodrigo tavares <[email protected]>
Cc: "[email protected]" <[email protected]>
Enviadas: Quinta-feira, 31 de Janeiro de 2013 11:17
Assunto: Re: Duplicate attributeType: "2.5.4.35"
On Thu, 31 Jan 2013, rodrigo tavares wrote:
> In my samba.schema, added the atribute userPassword.
[...]
> root@fileserver02:/etc/ldap/schema# slapindex -v
[...]
> /etc/ldap/schema/samba.schema: line 195 attributetype: Duplicate
> attributeType: "2.5.4.35" slapindex: bad configuration file!
>
> What's wrong ?
userPassword is one of a handful of attributes that's hard-coded into slapd(8).
See servers/slapd/schema_prep.c.
Anyway, yes, you're "duplicating" userPassword via multiple definitions: the
hard-coded definition and your samba.schema definition. The hard-coded
definition should serve fine, just remove it from samba.schema.
Why are you putting these in samba.schema anyway? Editing upstream schema isn't
best practice. If you need a local schema file, make one from scratch, don't
glob on to somebody else's definitions...
