[Date Prev][Date Next]
Re: "index delete failed" and "Inappropriate matching"
Do you know what COLLECTIVE actually means in an attribute
definition? If not, it would be quite unwise to set it.
Collective attributes are not supported in OpenLDAP 2.0.8.
The next release of 2.0 will refuse to accept attributes
defined as COLLECTIVE.
See draft-zeilenga-ldap-collective-00.txt or X.500 for
further information on collective attributes, available
Your problem is that the attribute in question is defined
without an equality matching rule and hence certain operations
(such as add/delete of individual values) is limited.
At 06:15 PM 5/16/01, Paul Jakma wrote:
>On Wed, 16 May 2001, Jaron Omega wrote:
>> Try this in the schema, I got this too, your trying to have
>> multiple attributes with different values?
>yes... netgroups would be fairly useless otherwise. :)
>> Hope this helps.
>> attributetype( 184.108.40.206
>> NAME 'nisnetgrouptriple'
>> DESC 'I can exists many times in a single entry'
>> EQUALITY objectIdentifierMatch
>> ORDERING caseIgnoreOrderingMatch
>> SYNTAX 220.127.116.11.4.1.1418.104.22.168.40 COLLECTIVE )
>indeed, adding the equality, ordering and collective parts worked.
>however, this must surely be a bug in RFC2252, the RFC which the
>nis.schema file says it implements?
>> Jaron Omega
>Paul Jakma firstname.lastname@example.org email@example.com
>PGP5 key: http://www.clubi.ie/jakma/publickey.txt
>Why is the alphabet in that order? Is it because of that song?
> -- Steven Wright