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

Re: Loading LDAP schema files into cn=config

To: Chan Wilson <chanwilson@gmail.com>
Subject: Re: Loading LDAP schema files into cn=config
From: Quanah Gibson-Mount <quanah@zimbra.com>
Date: Sat, 02 Jul 2011 12:24:53 -0700
Cc: openldap-technical@openldap.org
Content-disposition: inline
In-reply-to: <BANLkTim6XDfLF4jBxiSYYv=5HkoAQvrtxg@mail.gmail.com>
References: <4E0AFDB9.7090208@siriusit.co.uk> <BANLkTikivmMm=FnGgCuWh2BpOK5omjPeyw@mail.gmail.com> <4E0EB8AA.1090309@symas.com> <BANLkTim6XDfLF4jBxiSYYv=5HkoAQvrtxg@mail.gmail.com>

--On Saturday, July 02, 2011 1:36 PM -0500 Chan Wilson<chanwilson@gmail.com> wrote:

And recognizing that emergencies *do* happen, and having a Plan of Action
is key to responding to emergencies correctly, what *is* the proper way
to manually edit cn=config?Â Particularly in a replicated RTC setup?ÂÂ
I figure it's something like

- shut off slapd
- edit the ldif.Â
ÂÂ - remove | edit one or more of the operational attributes
Â- turn on slapd


slapmodify would be the correct thing to use (Currently only in HEAD).

Oddly, I followed the test050 procedure in creating my bootstraps
and based from that did expect it to work.

I do this routinely to set up replication, and it works fine for me withouta restart. That's with 2.4.21, 2.4.23, 2.4.25 and 2.4.26.


--Quanah

--

Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration

References:
- Re: Loading LDAP schema files into cn=config
  - From: Chan Wilson <chanwilson@gmail.com>
- Re: Loading LDAP schema files into cn=config
  - From: Howard Chu <hyc@symas.com>
- Re: Loading LDAP schema files into cn=config
  - From: Chan Wilson <chanwilson@gmail.com>

Prev by Date: Re: Loading LDAP schema files into cn=config
Next by Date: Re: Loading LDAP schema files into cn=config
Index(es):
- Chronological
- Thread