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

Re: loglevel question

On Mon, 22 Oct 2007, Hallvard B Furuseth wrote:

> Quanah Gibson-Mount writes:
> >--On Sunday, October 21, 2007 1:55 PM +0200 Piotr Wadas
> ><pwadas@jewish.org.pl> wrote:
> >> Can I set "loglevel" option only for particular database, or
> >> all databases of particular backend (any slapd version) ?
> >> man slapd-<backend> does not mention about it, and the loglevel
> >> option is marked global in slapd manpage, however

> >>
> >> Options described in this section apply to all backends, unless
> >> specifically overridden in a backend definition."

> Right, the loglevel is a global variable.  And that doesn't look
> like it could be easily changed either, since much of the logging
> happens outside of the backend which handles the meat of the
> operation.

> > Did you read the manpage for the backend in question to see if it
> > could be overridden?
Yes, like mentioned, man slapd-<backend) - meaning any backend manpage - 
does not mention about it. I actually care about shell backend currently,
anyway such feature would be really useful, probably regarding 
a suffix, rather than particular backend. If much of the logging
happens outside of the backend - it means it could be theoretically
possible, to focus logging on particular suffix. Also, sizelimit and
timelimit could apply to particular suffix (?), anyway, for now,
sizelimit and timelimit can be set (AFAIR) on client side, while
logging - reasonably - cannot be. 

Probably implementing another configuration option, or some overlay (?), 
would be easiest way to implement suffix-related (not 
database/backend-related), independent logging, or independent 
size/timelimit override... Interesting, that global loglevel option
can include value of 1024, related only to shell backend.

Anyway, seems clearly to me, that suffix/backend logging is currently
unavailable, thanks anyway.