Re: extending schema

[Adam Grochowski <adam.grochowski@mail.tju.edu>]

Thanks for your help guys,
what it turns out is I had tju.schema above inetorgperson.schmema in my 
slapd.conf.  I didn't know order of the schemas mattered, but apparently 
they do.
Adam

 On Tue, 14 May 2002, Jatin Nansi wrote:

> inetorgperson.schema depends on core.schema being included.
> so put in core.schema. Check the first couple of lines in 
> inetorgperson.schema.
> 
> Jatin
> 
> 
> On Tuesday 14 May 2002 03:41, Rohit Dewan wrote:
> > I think you need to include core.schema as well.
> >
> > Rohit
> >
> > -----Original Message-----
> > From: owner-openldap-software@OpenLDAP.org
> > [mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Adam
> > Grochowski
> > Sent: Monday, May 13, 2002 12:19 PM
> > To: openldap-software@OpenLDAP.org
> > Subject: extending schema
> >
> > Hi,
> > I'm trying to define my own OC's and I've run into a bit of a snag.
> > Here's my entry
> >
> > objectclass ( 1.3.6.1.4.1.13127.2.2.100 NAME 'tjuPerson'
> > 	SUP	( inetOrgPerson ) STRUCTURAL
> > 	MUST ( uid $ userPasswordControls )
> > 	MAY ( attrVisibility $ barcodeID $ tjuAccts $ tjuRole $
> > description ) )
> >
> > In slapd.conf I have included both my new file (tju.schema) and
> > inetorgperson.schema.  Yet when I try to start openldap (2.0.11-13)
> > I get
> >
> > /etc/openldap/schema/tju.schema: line 6: ObjectClass not found:
> > "inetOrgPerson"
> >
> >
> > Am I missing something?
>