On Thu, May 29, 2003 at 10:07:48AM -0500, John Beamon wrote:
time and never relinquishes it. It does not grab "91%" and hold that
number, but it maintains a 0.0% idle CPU. This is a recent observation
I can think of two possible causes regarding configuration errors:
1) The slave is also configured to replicate to the master. This will
get you a nice loop, and the replication log will never empty.
2) Have the master use a reserved name for the replogfile. Slurpd uses
slurpd.replog for its private copy. If you happen to set the replog
directive to slurpd.replog, then slurpd will loop.