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

Re: Concerns with OLC (cn=config) for editing schema, ACLs, and deleting entries

To: openldap-technical@openldap.org
Subject: Re: Concerns with OLC (cn=config) for editing schema, ACLs, and deleting entries
From: Buchan Milne <bgmilne@staff.telkomsa.net>
Date: Fri, 23 Mar 2012 11:00:31 +0200
Cc: Chris Hiestand <chiestand@salk.edu>, Howard Chu <hyc@symas.com>
In-reply-to: <4F686194.1040105@symas.com>
References: <315EABE9-81AD-4595-AAD5-6732BCCE0472@salk.edu> <4F686194.1040105@symas.com>
User-agent: KMail/1.13.7 (Linux/2.6.38.8-desktop-9.mga; KDE/4.6.5; x86_64; ; )

On Tuesday, 20 March 2012 12:53:08 Howard Chu wrote:

> The purpose of cn=config is to support configuration changes on a server
> without causing any service outage. Supporting Deletes in cn=config is
> fundamentally opposed to this goal. E.g., deleting an olcDatabase entry
> cannot be seen as anything other than a service outage - you were serving
> a database a second ago, now it's gone.

On a server serving multiple databases, removing one of the databases is not 
necessarily a service outage. I would prefer (when I can clean up a legacy 
database, once the last of the legacy software that uses it is migrated) not 
to have outages on the other 3 databases in use.

Regards,
Buchan

Follow-Ups:
- Re: Concerns with OLC (cn=config) for editing schema, ACLs, and deleting entries
  - From: Michael Ströder <michael@stroeder.com>
- Re: Concerns with OLC (cn=config) for editing schema, ACLs, and deleting entries
  - From: Howard Chu <hyc@symas.com>

References:
- Concerns with OLC (cn=config) for editing schema, ACLs, and deleting entries
  - From: Chris Hiestand <chiestand@salk.edu>
- Re: Concerns with OLC (cn=config) for editing schema, ACLs, and deleting entries
  - From: Howard Chu <hyc@symas.com>

Prev by Date: Re: Line breaks in Directory String values
Next by Date: Re: Concerns with OLC (cn=config) for editing schema, ACLs, and deleting entries
Index(es):
- Chronological
- Thread