[Date Prev][Date Next]
Re: (ITS#4615) Possible bug in access log overlay with distributed databases
This is all about the glue code, not specific to the accesslog overlay.
I guess it's a bug, certainly it's not what I would want the behavior to
> Full_Name: Ski Kacoroski
> Version: 2.3.24
> OS: Debian Linux Sarge 3.1
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (18.104.22.168)
> I have the following setup:
> dc=nsd, dc=org # superior database with accesslog nsdlog
> -- ou=people # ou in superior database
> -- ou=hosts # subordinate database with accesslog hostslog
> When I make a change, search, add, delete to an object in
> "ou=people,dc=nsd,dc=org", I get logs in nsdlog only. This is makes sense
> When I do a search with base "dc=nsd,dc=org" and scope of base I get an entry in
> nsdlog only. This makes sense. If I change the scope to one or sub I get an
> entry in nsdlog and hostslog. This also makes sense to me.
> When I do the following search:
> ldapsearch -x -b "ou=hosts,dc=nsd,dc=org" -h localhost "(uid=test)" with any -s
> option I get entries in both nsdlog and hostslog even though the search should
> just be in the "ou=hosts,dc=nsd,dc=org" database.
> Question is why I am still getting search entries in the nsdlog? Is this
> expected behaviour?
-- 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/