Re: Object Class Violation

Adam Tauno Williams said:
>> On two different systems, FC4 and SuSE 9, I get this error. I've
>> traced it in the logfiles to the following ldap error:
>> invalid structural object class chain (inetOrgPerson/account)
>> This appears to be a bug in the software, since there is indeed no
>> attribute "account" in inetorgperson schema. Is there a fix?
>
> "account" is an objectclass, as in inetOrgPerson.  Both are structural
> and not of the same inheritance chain, so their coexistence is illegal
> unless sealed by an objectclass that subsequently descends from both
> of
> them.
>
> objectclass ( 1.3.6.1.4.1.6921.1.12
>     NAME 'mHybridPerson'
>       DESC 'Combine several objectclasses to support multiple MUAs'
>     SUP ( inetOrgPerson $ officePerson $ evolutionPerson )
> STRUCTURAL )
>
> objectclass ( 1.3.6.1.4.1.6921.1.24
>     NAME 'mHybridUserAccount'
>       DESC 'Combine mHybridPerson and account'
>     SUP ( mHybridPerson $ account )
>     STRUCTURAL )

I think I understand what you're saying. You answer is probably 100%
correct, but it doesn't help me solve the problem. How do I find the
Object Class Violation? I presume I have two conflicting schemas,
however I haven't a clue the way to determine the one I need to
remove.

Can someon help, or is the question too simple to answer?


-- 
Neil Schneider                              pacneil_at_linuxgeek_dot_net
                                           http://www.paccomp.com
Key fingerprint = 67F0 E493 FCC0 0A8C 769B  8209 32D7 1DB1 8460 C47D
Secrecy, being an instrument of conspiracy, ought never to be the
system of a regular government.
- Jeremy Bentham, jurist and philosopher (1748-1832)