[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
schemacheck and structuralObjectClass
- To: openldap-software@OpenLDAP.org
- Subject: schemacheck and structuralObjectClass
- From: Ben Beuchler <insyte@gmail.com>
- Date: Wed, 18 May 2005 10:24:06 -0500
- Content-disposition: inline
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=J6gOZ6ws4c9YU4MFYA3uf6BqJuI6aWbL/Ok9URvP2P/VF4sZk1JJGafUx3+L+ZtMN2dT2QuINfY8+TYQm4tMgCXGmm3KVPfWlKk7lbgXDvN7jH3ZBnFVlseaVfrkPm/0kyHl3IsqG7rj+qgKnNITPnXqByaRuReBLVsrwsBka80=
For some reason, the operational attribute "structuralObjectClass" is
not automatically created if an entry is added when "schemacheck" is
off. This, of course, results in any attempt to modify an entry
created before I turned on "schemacheck" to dump out the "No
structuralObjectClass operational attribute" error.
Is that expected behavior? If I'm creating accounts with
"schemacheck" turned off, should I be manually adding the
"structuralObjectClass" entry?
Thanks!
-Ben