https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7690
RW <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from RW <[email protected]> --- (In reply to jidanni from comment #0) > man spamd says: > > -m number , --max-children=number > This option 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. That's misleading as it's only correct for the legacy round-robin pre-fork mode, otherwise it's just a limit. > OK, but setting this to 1 will cause logs to have > > Thu Jan 24 22:42:55 2019 [18861] info: prefork: server reached > --max-children setting, consider raising it > > with no way to turn off the message. What if the user always processes > his spam one by one serially, not in parallel? So please give him a way > to disable this particular warning. In my experience you don't get this if you run one spamc instance at a time - you may need to reconfigure your glue. spamd isn't the right place to throttle a queue. As far as the rest is concerned, the settings are fairly self-explanatory. If anyone wants to know what happens with weird settings they can try them or read the perl. The documentation is already TL;DR for many people. The one exception to this is that fact that the number of children wont drop below max-spare. IMO the behaviour should be changed to conform with common sense so the mimimum is MAX(min-children, min-spare). -- You are receiving this mail because: You are the assignee for the bug.
