ITS#6493,ITS#6515

diff --git a/CHANGES b/CHANGES
index bc08483a030e264d2f143a05c2f76bf38a474bc5..d6df7fd781b0c90c752772c3c387f1db573004c8 100644 (file)
--- 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 0c94df5ee9e88f17d75711c946d93cbed3120d05..8f9601c8819499552885283f567979b7c27bf4e1 100644 (file)
--- 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!}}