Re: what is wrong with this ldif file?

[Mark Hutchinson <markh@cybersurf.com>]

You sound right on this.  Maybe just sloppy ldif creation.  I took it from a 
qmail-ldap how to.

I added the information you suggest:

dn: dc=thegameqube,dc=com
objectclass: top
objectclass: dcObject
dc: thegameqube
 
dn: ou=accounts,dc=thegameqube,dc=com
objectclass: top
objectclass: organizationalUnit
ou: accounts

But now I get this:

Enter LDAP Password:
adding new entry "dc=thegameqube,dc=com"
ldapadd: update failed: dc=thegameqube,dc=com
ldap_add: Object class violation (65)
        additional info: no structural object classes provided


I think we are close.  Any ideas?

Thanks allot for the assistance!

Mark
-- 
Mark Hutchinson
Senior Unix Engineer
Cybersurf Corporation
300, 1144 29 Avenue N.E.
Calgary, Alberta.  T2E 7P1
Phone: 403-777-2000 Ext.242
Email: markh@cybersurf.com


Quoting Lucca <lucca@accela.net>:

> On Fri, 19 Jul 2002 14:49:03 -0600
> Mark Hutchinson <markh@cybersurf.com> wrote:
> 
> > dn: dc=thegameqube,dc=com
> > objectclass: top
> 
> > dn: ou=accounts,dc=thegameqube,dc=com
> > objectclass: top
> > objectclass: organizationalUnit
> > ou: accounts
> 
> > ldap_add: Undefined attribute type (17)
> > 	additional info: dn: attribute type undefined
> 
> The attributes you specify in the DN must be present on the object
> itself.  (Should be, some versions seem to let you slip around this
> with unfortunate consequences)
> 
> dn: dc=thegameqube,dc=com
> objectclass: top
> objectclass: dcObject
> dc: thegameqube
> 
> dn: ou=accounts,dc=thegameqube,dc=com
> objectclass: top
> objectclass: organizationalUnit
> ou: accounts
> 
> and so on...
> 
> Matthew Backes
> lucca@accela.net
>