On 2.64 I'm not sure what's the forking process. It may be modestly
painful. But an extra 3 seconds every hour and a half is no big tax
to pay on your machine's performance unless you're trying to play
precision timing games in the background. Heck, you could run raw
spamassassin and not really see any performance loss on your machine
at a puny one message every 6 minutes, I think you said as your rough
message level. The only machine on which I've had problems with the
1500 messages a day traffic level is the 66 MHz Pentium with 256 M
of memory that was pretty much swamped. It took 20 seconds to 30 seconds
to process a message.
I believe prefork simply means that spamd used up its child, which lives
for one message worth of processing, and that it is creating a new child
ahead of time so it is ready for the next message.
{^_^}
----- Original Message -----
From: "Chris" <[EMAIL PROTECTED]>
Thanks Joanne, what has me wondering about the setup is that in GKrellm it
will show 257mb of ram free and 537mb of swap free, I do a service
spamassassin restart and free ram jumps up to 350mb and free swap jumps to
595. I used to have a cron job I ran that daily would restart SA, that was
I think with 2.63 or 2.64. I also notice that sometimes once an hour and
sometimes 5 or 6 times an hour my syslog shows:
spamd[1061]: prefork: child states: II
I may have not read the correct manpage but I can't find an explanation for
prefork. Is it respawning the child processes at that time?
