[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: Server ignores changes to schema OID
Thanks for the advice. I was already restarting the server so I went
back and retraced my steps.
I tracked down the problem to my management tool (phpLDAPadmin). It
turns out the management tool was caching the schema on the client
side. So, even when I did had my new OID number correctly installed and
working, it was still reporting the stale OID numbers. Once I figured
out how to disable schema caching on my client, I was golden.
-Chris
On Oct 30, 2004, at 11:56 AM, Hallvard B Furuseth wrote:
Chris Irvine writes:
I started developing and testing a some experimental schema using the
reserved 1.1 OID block. Now that I have received my official IANA OID
number, I went back to my schema definition and updated the OID for
some definitions. After updating the definition the server is still
reporting the old 1.1 OID numbers for my custom objectClass.
Restart the server. The schema is read when the server starts.
But first I think you need to rebuild the indices (with sbin/slapindex)
while the server is down. The syntax OID seems to be part of the hash
key which is used with an index.
--
Hallvard
--------------------------------------------------------------
Chris Irvine On-line store-> http://www.tfaw.com/
Director of Information Technology phone: 503-652-8815
Dark Horse Comics, Inc. http://www.darkhorse.com/
mailto:chrisi@darkhorse.com spam mailto:misterX@darkhorse.com
PGP Key ID: 0x0263648A
PGP F.P. 8CEF 1BC8 F763 DF79 6F38 3156 EA30 50DF 0263 648A