Hello, 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
"GLOBAL CONFIGURATION OPTIONS Options described in this section apply to all backends, unless specifically overridden in a backend definition."
Regards, Piotr
--On Sunday, October 21, 2007 1:55 PM +0200 Piotr Wadas pwadas@jewish.org.pl wrote:
Hello, 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
"GLOBAL CONFIGURATION OPTIONS Options described in this section apply to all backends, unless specifically overridden in a backend definition."
Did you read the manpage for the backend in question to see if it could be overridden? AFAIK, that is not possible with loglevel, if you want to save yourself some time.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
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
"GLOBAL CONFIGURATION OPTIONS Options described in this section apply to all backends, unless specifically overridden in a backend definition."
[Rearranging reply]:
AFAIK, that is not possible with loglevel, if you want to save yourself some time.
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?
No, what slapd.conf(5) calls a "backend definition" a bit earlier is a section of slapd.conf starting with "backend <foo>". And what it means is apparently either that or a "database <foo>" section, at least in the case of "sizelimit" and "access" statements. Could use some clarification, I'll file a documentation ITS for it.
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
"GLOBAL CONFIGURATION OPTIONS 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. P.
Piotr Wadas pwadas@jewish.org.pl writes:
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:
[...]
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.
You may have a look at accesslog overlay which logs database related operations, man slapo-accesslog, or auditlog overlay, man slapo-auditlog.
-Dieter
openldap-software@openldap.org
-
Dieter Kluenter -
Hallvard B Furuseth -
Piotr Wadas -
Quanah Gibson-Mount