Theo Van Dinter <[EMAIL PROTECTED]> writes: > --qnK4RqISe3HuYx1/ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > I was thinking about this idea this morning. Instead of fork()ing off > a process per incoming message, what if we initially fork()ed off -m > spamd processes, and in the same way we do mass-check w/ multiple procs, > we call out to the children as work requests come in?
spamd forks off one process per incoming message? (I should disclose that I don't run spamd.) It's crazy to fork for every check for servers written in C (since the days of NCSA httpd). In Perl it's serious nutball material. 100% agreement that we should change this. It might make sense to generalize how it works and share code between mass-check and spamd. Daniel -- Daniel Quinlan anti-spam (SpamAssassin), Linux, http://www.pathname.com/~quinlan/ and open source consulting
