Anton Aylward wrote:
On 05/07/2014 12:37 AM, Per Jessen wrote:
Carlos E. R. wrote:
On Monday, 2014-05-05 at 12:29 -0700, Linda Walsh wrote:
** Significantly: "--max-conn-per-child=1"
It is not in the spamd manual.
It is in mine, but my spamassassin is backlevel and built from source:
NAME spamd - daemonized version of spamassassin
SYNOPSIS spamd [options]
Options:
[snip] -m num, --max-children=num Allow maximum num children --min-children=num Allow minimum num children --min-spare=num Lower limit for number of spare children --max-spare=num Upper limit for number of spare children --max-conn-per-child=num Maximum connections accepted by child before it is respawned
So what's the significance of this?
Like many others here I run a single user system, its just me who who uses it.
I bring in my mail using fetchmail which feeds into procmail. The procmail makes use of spamc, the client that calls on spamd.
It processes one mail message at a time. I can see that by watching the logs with 'tail -f'.
I emphasise: ONE MESSAGE AT A TIME.
[snip]
So why have many spamd children?
I can see the logic in having one forked off ready, but having 4? Having 8? Yes that would make sense in a richly multi-user context where there are going to be many users/threads calling on it in parallel. But that doesn't apply for my context.
If those are the default, just change them to suit your context :-) Anton, I'm sure you're making a point here, but I can't see what it is? -- Per Jessen, Zürich (14.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org