You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Chris <cp...@earthlink.net> on 2005/08/14 23:35:43 UTC
SIGCHILD
What determines how often the current spamd child process is hit by a SIGCHILD
command?
--
Chris
Registered Linux User 283774 http://counter.li.org
16:33:18 up 11 days, 1:09, 2 users, load average: 1.58, 1.71, 1.04
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BOFH excuse #374:
It's the InterNIC's fault.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: SIGCHILD
Posted by Chris <cp...@earthlink.net>.
On Sunday 14 August 2005 05:50 pm, Loren Wilton wrote:
> > What determines how often the current spamd child process is hit by a
>
> SIGCHILD
>
> > command?
>
> --max-conn-per-child I expect for the most part.
>
> Personally I think the child should be doing its own counting instead of
> the parent hammering it over the head. However, that ain't how it works
> currently.
>
> Loren
Thanks Loren, I was wondering because there seems to be no rhyme or reason as
to when it happens.
--
Chris
Registered Linux User 283774 http://counter.li.org
17:55:53 up 11 days, 2:32, 2 users, load average: 0.67, 0.46, 0.35
Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Don't let people drive you crazy when you know it's in walking distance.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Re: SIGCHILD
Posted by Loren Wilton <lw...@earthlink.net>.
> What determines how often the current spamd child process is hit by a
SIGCHILD
> command?
--max-conn-per-child I expect for the most part.
Personally I think the child should be doing its own counting instead of the
parent hammering it over the head. However, that ain't how it works
currently.
Loren