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

Re: SLAPD_CONF_UNKNOWN_BAILOUT

To: Aaron Richton <richton@nbcs.rutgers.edu>
Subject: Re: SLAPD_CONF_UNKNOWN_BAILOUT
From: Pierangelo Masarati <ando@sys-net.it>
Date: Thu, 08 Sep 2005 01:30:37 +0200
Cc: openldap-devel@OpenLDAP.org
In-reply-to: <Pine.SOL.4.58.0509071903370.9763@toolbox.rutgers.edu>
References: <Pine.SOL.4.58.0509071903370.9763@toolbox.rutgers.edu>
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 CentOS/1.7.8-1.1.3.1.centos3

Aaron Richton wrote:

SLAPD_CONF_UNKNOWN_BAILOUT is wrapped in LDAP_DEVEL as of today. Any opinions on how dangerous it may be, or if it might be mainstreamed in the foreseeable future? (I just caught a config typo that's been around for weeks, and it was rather annoying that religiously running "slaptest" after every edit was useless because I don't run "slaptest -d 64".)

I routinely use it (I'm using HEAD for a few projects in pre-production running heavy stress tests) and I'm quite happy with it. My only concern is how many persons will complain about it because they're just happy with their malformed files. I vote for moving it outside of LDAP_DEVEL.

p.


   SysNet - via Dossi,8 27100 Pavia Tel: +390382573859 Fax: +390382476497

References:
- SLAPD_CONF_UNKNOWN_BAILOUT
  - From: Aaron Richton <richton@nbcs.rutgers.edu>

Prev by Date: SLAPD_CONF_UNKNOWN_BAILOUT
Next by Date: Re: SLAPD_CONF_UNKNOWN_BAILOUT
Index(es):
- Chronological
- Thread