Hello Everybody, Thank you for answering my question. I am still confused... If schema files are never used directly, while LDIFs are used instead; why is there no tool which produces LDIF files suitable for ldapadd(1) or/and ldapodify(1)?
LDIF is LDIF.. I.e., it's a standard. You can write a tool if you see fit, I suppose?
Is it recommended to run a schema to LDIF conversion, then to manually edit the LDIF file[s]?
That is a possible method to use. I personally don't do that. We have a tool @ zimbra that auto-generates our schema from an XML input.
I tried to add one optional attribute - ipPhone. Made a schema (dummy)
then converted to below file:
dn: cn=dummy,cn=schema,cn=config
changetype: add
objectClass: olcSchemaConfig
cn: dummy
dn: cn=dummy,cn=schema,cn=config
changetype: modify
# changetype: add
add: olcAttributeTypes
olcAttributeTypes: {0}( 1.3.6.1.4.1.4203.666.100.123 NAME 'ipPhone'
DESC 'ip telephone internal or routable number' SUP telephoneNumber )
-
add: olcObjectClasses
olcObjectClasses: {0}( 1.3.6.1.4.1.4203.666.100.1 NAME 'dummyPerson'
DESC 'Dummy-server user' SUP inetOrgPerson STRUCTURAL MAY ipPhone )
Is this right?
Did it work? Or did you get an error? --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration