From: Chris [mailto:[EMAIL PROTECTED]
>
> On Monday 22 November 2004 09:29 am, Bowie Bailey wrote:
> > From: Chris [mailto:[EMAIL PROTECTED]
> >
>
> > You missed something...
> >
> > SA 3.0.1 pre-spawns it's children. Rather than spawning a child for
> > each incoming connection, it pre-spawns a
On Monday 22 November 2004 09:29 am, Bowie Bailey wrote:
> From: Chris [mailto:[EMAIL PROTECTED]
>
> You missed something...
>
> SA 3.0.1 pre-spawns it's children. Rather than spawning a child for
> each incoming connection, it pre-spawns a set number of children to
> deal with the connections.
From: Chris [mailto:[EMAIL PROTECTED]
>
> I've been meaning to ask this ever since I upgraded to 3.0.1 but
> keep forgetting. Under 2.63 I always had one spamd process running
> and when Kmail called spamc a spamd child was spawned, when
> processing was finished, that child process died. With 3
On Saturday 20 November 2004 12:34 pm, Gary W. Smith wrote:
> Try
> -m 1
>
> > I've been meaning to ask this ever since I upgraded to 3.0.1 but keep
> > forgetting. Under 2.63 I always had one spamd process running and
>
> when
>
> > Kmail called spamc a spamd child was spawned, when processing wa
Try
-m 1
> -Original Message-
> From: Chris [mailto:[EMAIL PROTECTED]
> Sent: Friday, November 19, 2004 6:09 PM
> To: users@SpamAssassin.apache.org
> Subject: Number of spamd process running
>
> I've been meaning to ask this ever since I upgraded to 3.0.1 but
I've been meaning to ask this ever since I upgraded to 3.0.1 but keep
forgetting. Under 2.63 I always had one spamd process running and when
Kmail called spamc a spamd child was spawned, when processing was finished,
that child process died. With 3.0.1 I have two spamd process continuously
ru
