[Bug 3276] Invalid max-children (-m) option description

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=3276





------- Additional Comments From jm@jmason.org  2004-04-16 10:18 -------
hmm.  this is a new feature that Theo just added -- doco below.  I'd suggest
making it two separate options, IMO, so that we can use GetOptions()' parsing
code, and also because the functionality is slightly separate from
--max-children.  The good news is that I don't think it needs to be a short
option, a --long-option alone would be fine I think.  --max-conns-per-child?

       -m number [ , number ] , --max-children=number[ , number ]
           The first number specifies the maximum number of children to spawn.
           Spamd will spawn that number of children, then sleep in the
           background until a child dies, wherein it will go and spawn a new
           child.

           Incoming connections can still occur if all of the children are busy,
           however those connections will be queued waiting for a free child.
           The minimum value is 1, the default value is 5.

           Please note that there is a OS specific maximum of connections that
           can be queued (Try "perl -MSocket -e'print SOMAXCONN'" to find this
           maximum).

           The second number specifies the maximum number of connections each
           child should process before dying and letting the master spamd pro-
           cess spawn a new child.  The minimum value is 1, the default value is
           1000.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.