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

RE: Slurpd and cpu usage



--On Monday, August 16, 2004 1:11 AM -0400 James Courtney <Jcourtney@inphonic.com> wrote:

Don't they share the file in a producer->consumer fashion with slapd
writing and slurpd reading/truncating?  There's only one config option
for this so I have to assume that there's only one file since they
(slapd and slurpd) share that config file.  I'll try changing the
location though and see what we get.


Kind of.

Slapd writes out the replication out put to the file/location specified by the "replog" command.

Slurpd reads that file and copies it to the directory specified by the "-t" option at startup, to a file named slurpd.replog, and then truncates the slapd replog file.

So if the "-t" option points to the same place as where you are writing the slapd replog file, or if your default for slurpd is the same place as where you are writing the slapd replog file, and you name the slapd replog file "slurpd.replog", you are going to get a collision that sounds exactly like what you are seeing.

--Quanah

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