[Date Prev][Date Next]
Re: (ITS#4742) parameter unique_attributes and unknown attribute types
> firstname.lastname@example.org wrote:
>> Another possibility would be to always enable LDAP_DEBUG_CONFIG for the
>> tools. The only reason I suggest this is because I would prefer that
>> runtime configuration errors are only logged when specifically
>> requested, not at DEBUG_ANY. Since the error messages are already
>> returnes to the client in the protocol, it's not always necessary to log
>> them separately.
> The point is that I'd like to separate informative messages about
> configuration (LDAP_DEBUG_CONFIG) from __the__ message that described
> why slaptest failed (or slapd refuses to start). Right now, either you
> get all (which is annoying) or none (which is frustrating). Apparently,
> unless we hijack LDAP_DEBUG_NONE for the duration of config parsing, and
> OR it to all messages followed by "return ARG_BAD_CONF;", we need
> another LDAP_DEBUG_*.
OK. And we have usually used DEBUG_ANY for fatal messages of this type.
The point I'm making now is that config errors are no longer always
fatal; it depends on whether we're starting up or already running.
-- Howard Chu
Chief Architect, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc
OpenLDAP Core Team http://www.openldap.org/project/