[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Transaction logging and OpenLDAP
- To: openldap-software@OpenLDAP.org
- Subject: Transaction logging and OpenLDAP
- From: Tech Guy <techguymenlo@yahoo.com>
- Date: Fri, 11 Aug 2006 08:46:35 -0700 (PDT)
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=I9cy3BJW9mTZ0QX0egq5zkTfYRHAuSF20PdjuIhreTN2Dx2ZLtnErcuO/Qvm9AvkSuRYxFtlEr+CMO03fs/5huMqwZTyLLsqgkCi/zO+n06I3JCuxhls3E0qhlbuzafbUSdrcSwJ8dwsf+9YMAeumHkcFbeStMejDNvu19tJSPI= ;
Hi,
I understand that there have been several discussions
in the past about transaction logging on OpenLDAP. I
have a couple of questions in this matter that may or
may not have been addressed previously.
We are running BDBv4.4.20 and OpenLDAPv2.3.24.
1. Is there a way to completely stop transaction
logging in OpenLDAP, along the lines of "slapadd -q"?
>From reading BDB documentation, it appears that an
application can use BDB as a transactional or
non-transactional back-end.
2. Presently we have the following directives to
remove log files in slapd.conf:
checkpoint 5120 15
and in DB_CONFIG
set_flags DB_LOG_AUTOREMOVE
These directives reduce the logging in OpenLDAP but
under stress add's, a 10M log file is creates about
every two hours. Looking at db_stat, it appears the
checkpoint is not done as frequently. Is this unusual
and are we missing a setting?
We now have a cron job to force a checkpoint and
remove unwanted log files.
# Commit buffered active transactions to database
every mid-night
* 0 * * * /usr/bin/db_checkpoint -1 -h /data/ldbm
#Remove in-active log files ten minutes after
midnight.
10 0 * * * /usr/bin/db_archive -d -h /data/ldbm"
Looking for suggestions to avoid logging or an
efficient way to remove logs.
Thanks in advance for responses,
TechGuy
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com