You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by fe...@apache.org on 2004/09/09 16:25:43 UTC
svn commit: rev 43603 - spamassassin/trunk/lib/Mail/SpamAssassin
Author: felicity
Date: Thu Sep 9 07:25:43 2004
New Revision: 43603
Modified:
spamassassin/trunk/lib/Mail/SpamAssassin/ArchiveIterator.pm
Log:
try clearing up the opt_j tempfile/extra child distinction
Modified: spamassassin/trunk/lib/Mail/SpamAssassin/ArchiveIterator.pm
==============================================================================
--- spamassassin/trunk/lib/Mail/SpamAssassin/ArchiveIterator.pm (original)
+++ spamassassin/trunk/lib/Mail/SpamAssassin/ArchiveIterator.pm Thu Sep 9 07:25:43 2004
@@ -96,21 +96,25 @@
Specifies how many messages should be run at the same time, as well as the
method with which to scan for the messages.
-If the value is 0, the list of messages will be kept in memory, and
-only 1 message at a time will be processed by the wanted subroutine.
+If the value is 0, the list of messages to process will be kept in memory,
+and only 1 message at a time will be processed by the wanted subroutine.
Restarting is not allowed.
-If the value is 1, the list of messages will be kept in a temporary file,
-and only 1 message at a time will be processed by the wanted subroutine.
-Restarting is not allowed. A child process will be forked to determine the
-list of messages.
+If the value is 1, the list of messages to process will be kept in a
+temporary file, and only 1 message at a time will be processed by the
+wanted subroutine. Restarting is not allowed.
+
+If the value is 2 or higher, the list of messages to process will be kept
+in a temporary file, and the process will split into a parent/child mode.
+The option value number of children will be forked off and each child
+will process messages via the wanted subroutine in parallel. Restarting
+is allowed.
-If the value is 2 or higher, the list of messages will be kept in a
-temporary file, and the process will split into a parent/child mode.
-The option value number of children will be forked off and each child will
-process messages via the wanted subroutine in parallel. Restarting is
-allowed. A separate child process will be forked to determine the list
-of messages.
+B<NOTE:> For C<opt_j> >= 1, an extra child process will be created to
+determine the list of messages, sort the list, everything as appropriate.
+This will keep the list in memory (possibly multiple copies) before
+writing the final list to a temporary file which will be used for
+processing. The list generation child will exit, freeing up the memory.
=item opt_n