[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: slurpd.replog never emptied

To: daniel@ncsu.edu, openldap-software@OpenLDAP.org
Subject: Re: slurpd.replog never emptied
From: Quanah Gibson-Mount <quanah@stanford.edu>
Date: Tue, 31 Aug 2004 13:03:48 -0700
Content-disposition: inline
In-reply-to: <Pine.GSO.4.60.0408311400510.6716@ghidora.unity.ncsu.edu>
References: <Pine.GSO.4.60.0408311400510.6716@ghidora.unity.ncsu.edu>

--On Tuesday, August 31, 2004 2:02 PM -0400 Daniel Henninger <daniel@unity.ncsu.edu> wrote:

Folk,

Is slurpd.replog (the copy that slurpd makes of the replog for itself)
supposed to never be emptied entirely?  I find that there's always a
couple of "towards the end" entries that are left in that file.  It
started out as just one but now there are multiple and slurpd definitely
seems to have no intention of processing them as is.  (by towards the end
I mean, the last couple of changes that were pushed out last time)  Is
this normal?  Is slurpd keeping them for some reason I'm not aware of?
Thanks!

From what I've seen, those are always the last entries slurpd processed,

and the next time it gets new changes, it'll create a new file, and leave the last few changes in there. It's normal behavior.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

References:
- slurpd.replog never emptied
  - From: Daniel Henninger <daniel@unity.ncsu.edu>

Prev by Date: Re: Multiple passwords. Configurable bind attribute. Etc..
Next by Date: Openldap scalability problems
Index(es):
- Chronological
- Thread