[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Changing schema OID values in cn=config

To: Quanah Gibson-Mount <quanah@zimbra.com>
Subject: Re: Changing schema OID values in cn=config
From: Nick Milas <nick@eurobjects.com>
Date: Mon, 28 Nov 2011 21:18:26 +0200
Cc: openldap-technical@openldap.org
In-reply-to: <BD3BEEF58FCFE11B29C63048@[192.168.1.23]>
References: <4ED3C067.4010608@eurobjects.com> <BD3BEEF58FCFE11B29C63048@[192.168.1.23]>
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0

On 28/11/2011 9:04 ÎÎ, Quanah Gibson-Mount wrote:

If you are using the latest OpenLDAP, I would suggest you get abacktrace of the hung process and file an ITS. I would note thatchanging an OID on an existing schema is a bit of an odd thing to do.

I am using 2.4.26. I'll try to do a core dump and file an ITS per yourinstructions. Or this would be acceptable only with the latest version(.28) ?

I did this change as part of a test, because - surprisingly - ApacheDirectory Studio did not work properly with OID values like xxx.000,xxx.001 etc.

You may want to see: https://issues.apache.org/jira/browse/DIRSTUDIO-748

Nick

Follow-Ups:
- Re: Changing schema OID values in cn=config
  - From: Quanah Gibson-Mount <quanah@zimbra.com>

References:
- Changing schema OID values in cn=config
  - From: Nick Milas <nick@eurobjects.com>
- Re: Changing schema OID values in cn=config
  - From: Quanah Gibson-Mount <quanah@zimbra.com>

Prev by Date: Re: Changing schema OID values in cn=config
Next by Date: Re: Changing schema OID values in cn=config
Index(es):
- Chronological
- Thread