From: "John Fleming" <[EMAIL PROTECTED]>
> jdow said:
> > On another paw I note that most family tools are not left running
> > 24x7. If this is his case then a large portion of his 250 messages
> > may be coming in right after he boots. If he is setup to spawn
> > too many spamds then he could experience a memory crisis.
>
> That's not it. It's mostly a family/hobby server, but it functions
> "fairly professionally" - I just meant I'm not an ISP or big business
> with thousands of emails a day. The server's on 24/7/365 running
> Apache, Mailman and other common server stuff - but all at a VERY low
> activity/use level.
>
> I've reviewed my local.cf, and there was some duplication. I've
> removed the dupes and we'll see if that helps.
>
> I call spamd via spamc in procmail. I've read man spamc/d - I see
> where to limit the spamd children when using the spamd option, but I
> don't see how to pass that option on when using spamc. IOW, I don't see
how
> to limit spamd children when using spamc.
>
> Also, my procmailrc uses a lock file when evaluating the results of
> spamd - I guess that doesn't limit starting another spamd before
> that file has been evaluated? - John
Um, you do not limit with spamc. You simply setup the limit in spamd when
you start or restart it. It is probably a good idea to play with several
values to see which gives you performance closest to your desired
performance. As soon as you get enough spamds up to trigger paging the
overall performance will take a serious dive. To a fairly real extent
a limit of two or three is probably best for single processor systems
modulo how much time is spent computing compared to waiting on IO for
any given spamd. If it is heavily compute bound 2 might be optimum.
{^_^}
