[Date Prev][Date Next]
Re: Logging question
Howard Chu wrote:
Ski Kacoroski wrote:
Howard Chu wrote:
matthew sporleder wrote:
Matthew & Howard,
On 6/13/06, Ski Kacoroski <firstname.lastname@example.org> wrote:
Or you could look into the access log overlay. :)
That may be a good solution. Define two separate log databases, and
separate the machine and user data into two databases, using
subordinates to glue them together. Use an accesslog overlay on each
main database, logging to separate log databases.
Of course, the info in the accesslog may not be detailed enough for
debugging purposes. You'll have to review the log schema and decide
for yourself if it's adequate for your needs.
Ok, I have this working nicely with the following:
# Main logging database
# Hosts logging database
# Hosts database
# Main database
Tricks to getting it working were:
1. Comment out the accesslog overlay configuration until you create the
base object in the log databases or else slapd crashes
2. Be sure you have a rootdn and password set up on the log databases so
you can create the base object
3. Do not use the subordinate option on the main dc=nsd,dc=org database.
When I did this, the main database log picked up all the activity on
the hosts database. The downside to not using the subordinate option is
that I cannot do a recursive search from dc=nsd,dc=org into the ou=hosts
branch (this is fine with me). It is interesting though that if do:
ldapsearch -x -h localhost "(ou=*)"
it does not show the ou=hosts branch but if I do
ldapsearch -x -h localhost -b "ou=hosts,dc=nsd,dc=org" "(ou=*)"
it does show the ou=hosts branch.
Also jxplorer gets all confused and will not let me see the ou=hosts
branch at all. ldapsh however works fine with it.
Thanks again for all the help.
"When we try to pick out anything by itself, we find it
connected to the entire universe" John Muir
Chris "Ski" Kacoroski, email@example.com, 206-501-9803