Date: Fri, 10 Jan 2003 11:16:42 -0500 From: Scott Lambert <lambert@lambertfam.org> To: freebsd-isp@FreeBSD.ORG Subject: Re: SpamAssassin spawned 700 perl processes Message-ID: <20030110161642.GA4076@laptop.lambertfam.org> In-Reply-To: <6A4FC9DF-248E-11D7-93AF-000393BC25EC@hurrell.cc> References: <6A4FC9DF-248E-11D7-93AF-000393BC25EC@hurrell.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 10, 2003 at 09:56:51PM +1030, Greg Hurrell wrote: > Weird thing happened today to my mail server (FreeBSD 4.7-RELEASE-p2 > #6: Thu Nov 14 21:42:32 CST 2002). > > After 55 days of uptime, the machine suddenly went down like a town of > bricks. It appears that over a period of several hours, several > hundred perl processes built up -- all running either spamc or spamd > (from SpamAssassin). > > >/usr/bin/perl /usr/bin/spamd -x -i 203.2.192.76 -A 203.2.192.76 -r > >/var/run/spamd.pid -d Remote checks backed up on you and you went deep into swap. Use the -m argument to spamd. Unfortunately this causes some bad signal interaction with of the spamassassin subsystems (razor IIRC) that causes the master spamd process to die at random. So then you have to run it under something that will restart spamd if it dies. For instance: daemontools, init (via /etc/ttys) daemontools "run" script to run your config: #!/bin/sh exec /usr/local/bin/spamd -x -i 203.2.192.76 -A 203.2.192.76 -m (somenumber) daemontools "run" script for my config: #!/bin/sh exec /usr/local/bin/spamd -u spamd -a -q -x --allowed-ips=10.10.10.10,10.10.10.35 -i 0.0.0.0 -m 75 -H /etc/mail/spamassassin/ -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030110161642.GA4076>