From: Quanah Gibson-Mount <quanah@openldap.org>
Date: Mon, 19 Apr 2010 17:58:40 +0000 (+0000)
Subject: ITS#6493,ITS#6515
X-Git-Tag: OPENLDAP_REL_ENG_2_4_22~20
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=d1ebe15305a426b3229b183938e07b82a41c1814;p=openldap

ITS#6493,ITS#6515
---

diff --git a/CHANGES b/CHANGES
index bc08483a03..d6df7fd781 100644
--- a/CHANGES
+++ b/CHANGES
@@ -41,6 +41,7 @@ OpenLDAP 2.4.22 Engineering
 	Fixed contrib/nssov to use nss-pam-ldapd (ITS#6488)
 	Documentation
 		admin24 avoid explicity moduleload statements (ITS#6486)
+		admin24 broken link fixes (ITS#6493,ITS#6515)
 
 OpenLDAP 2.4.21 Release (2009/12/20)
 	Fixed liblutil for negative microsecond offsets (ITS#6405)
diff --git a/doc/guide/admin/schema.sdf b/doc/guide/admin/schema.sdf
index 0c94df5ee9..8f9601c881 100644
--- a/doc/guide/admin/schema.sdf
+++ b/doc/guide/admin/schema.sdf
@@ -105,7 +105,7 @@ You are, of course, free to design a hierarchy suitable to your
 organizational needs under your organization's OID. No matter what hierarchy you choose, you should maintain a registry of assignments you make.  This can be a simple flat file or something more sophisticated such as the {{OpenLDAP OID Registry}} ({{URL:http://www.openldap.org/faq/index.cgi?file=197}}).
 
 For more information about Object Identifiers (and a listing service)
-see {{URL:http://www.alvestrand.no/harald/objectid/}}.
+see {{URL:http://www.alvestrand.no/objectid/}}.
 
 .{{Under no circumstances should you hijack OID namespace!}}