Quoting Mike Jackson <mj(a)sci.fi>:
speedy zinc wrote:
> But I still can't figure out the differences between
> a STRUCTURAL and an AUXILIARY objectclass. Besdies the
> definition, they look similar to me.
It's part of the X.500 data model.
Every directory object can and must have only one structural object
class, and the other classes on that object have to be auxiliary. You
can only instantiate new objects with structural classes.
Example of an object:
structural class "car"
auxiliary class "europeanCar"
auxiliary class "raceCar"
europeanCar and raceCar are specializations (subclasses) of car.
Finally, FDS/RHDS do not enforce so-called "structural integrity". They
will allow you to e.g. create an entry which contains multiple
structural classes. OpenLDAP versions 2.1 and later prohibit this and
there is no way to disable it, even if you try. A server should give the
administrator the possibility of disabling structural integrity checking
personally i applaud openldap for doing this, even if it is a royal pain in the
ass. 90% of upgrading problems between openldap versions for me has come from
the applications written to use ldap that haven't designed their DITs properly.
as openldap has become more and more strict, almost all of these apps have
failed and then had to be fixed. if they'd been written properly in the first
place... you can disable checking for synclreps, but not the main master.
i suspect they found that by giving the option of turning off schema checking,
everyone was doing it as a 'quick fix'.
I recommend following the rules, even if FDS doesn't enforce them.
Fedora-directory-users mailing list