Matthew Weigel schrieb:
On Thu, 21 May 2009 12:54:30 +0000 (UTC), Stuart Henderson
<s...@spacehopper.org> wrote:
On 2009-05-21, Robson Caetano <inet1...@myself.com> wrote:
The problem is that changing the time of the hour or of the day you
fetch the blacklist will avoid concurrency but is not fault proof.
It isn't fault proof, but you should do it anyway.
Just to be clear... when spamd-setup is run in /etc/rc, with the -D flag,
it doesn't actually stick around, right? It just does its job in the
background so that grabbing updated black/whitelists can't hang the
machine.
And then the sample spamd-setup line in crontab runs it every hour, if
it's a good idea for everyone to change it wouldn't it be a good idea
to give an example that only runs e.g. once a day?
The main problem is that too many spamd-setups are running at the same
time. So doing this only once a day would only shift the problem.
My suggestion would be something like this patch to the default crontab
(this one is against 4.5-stable):
Index: crontab
===================================================================
RCS file: /cvs/src/etc/crontab,v
retrieving revision 1.15
diff -r1.15 crontab
23c23
< #0 * * * * /usr/libexec/spamd-setup
---
#0 * * * * sleep $((RANDOM % 120));
/usr/libexec/spamd-setup
This should take the load from the server providing the blacklist.
Kind regards,
Markus
