[Date Prev][Date Next]
RE: Slurpd Replog being constantly re-written
Not sure if I understand... Does it matter where the file
resides? I've been running with 2.0.25 Master/Slaves for a while on
another install, and under normal operation, slurpd truncates the file,
but slapd doesn't rewrite it. In this case, slurpd is truncating the
file, then slapd is re-writing it (or at least that what it looks like).
If I read what you've written another way, by default, RedHat
8.0 has the replog file specified as a remarked...
and I changed this to
to match what the old 1.2.13 install had. So what your saying is
Slurpd's 'private' file, is overwriting Slapd's file. So am I looking at
a difference between 1.2.x and 2.0.x, or have I just been dead-lucky
with other installs? Maybe only I can answer that best after a bit more
[mailto:owner-openldap-software@OpenLDAP.org] On Behalf Of Dave Horsfall
Sent: Wednesday, 11 December 2002 12:04 PM
To: OpenLDAP Software List
Subject: Re: Slurpd Replog being constantly re-written
On Wed, 11 Dec 2002, Garry Thomas wrote:
> I attempted this upgrade about a week ago, and hit a problem -
> the slurpd.replog file grew at an enormous rate (about 2Mbytes in
> 10 seconds) after an update. I did have the slapd.conf config item:
> replogfile /var/lib/ldap/replica/slurpd.replog
Ouch! That's the "master" replog file, which gets written to by slapd
and truncated by slurpd, in turn writing it to wherever you specified
slurpd's private directory (let me guess, "/var/lib/ldap"?)...
You need something like:
replogfile /usr/local/etc/openldap/replog/log .
(assuming slapd.conf lives in /usr/local/etc/openldap).
Dave Horsfall DTM VK2KFU email@example.com Ph: +61 2 9906-7866 Fx:
Corinthian Engineering, Level 1, 401 Pacific Hwy, Artarmon, NSW 2064,