On Fri, 5 Mar 2010 10:21:28 -0500 (EST) James Smallacombe <u...@3.am> wrote:
> On Fri, 5 Mar 2010, RW wrote: > > > On Thu, 4 Mar 2010 23:41:38 -0500 (EST) > > James Smallacombe <u...@3.am> wrote: > > > >> Installing from ports automatically installs perl > >> 5.10.1 which causes spamc children to run wild and basically, spamd > >> can't cope with it. > > > >> I don't need or want perl 5.bleeding.edge, 5.8.9 was working just > >> fine. I tried doing a 'make clean' then removing 5.10 and > >> correcting all the symlinks to point to 5.8.9, I tried running > >> use.perl system, but SA just keeps looking for 510 and installing > >> it when it doesn't find it. > > > > SpamAssassin's port makefile has "USE_PERL5_RUN= 5.8.8+", so it > > should work with 5.8.9, but if you build SA without perl installed, > > the default perl version of 5.10 is installed as a dependency. The > > correct way to revert to 5.8.9 is to remove 5.10 and put 5.8.9 back > > before reinstalling SA. However there may be a port in your system > > that needs 5.10+ - possibly a new SA dependency. > > > > FWIW I've been using 5.10 for a year without any problems, it's now > > the default in FreeBSD and FreeBSD is very conservative, it's far > > from bleeding edge. > > > > When you say that spamc children run wild I presume you mean spamd > > children. Are you using --round-robin with spamd? If so try using > > the default scaling instead. When I was playing around with spamd I > > noticed that round-robin caused the number of children to run away > > and lock-up at "max-children" > > I actually meant spamc's that had no spamd children to talk to. It > seems the ports version of SA replaced my original sa-spamd startup > script, which raised the max children from (default?) of 5 to 30. sa-spamd doesn't define the number of children, if you want spamd to start with non-default settings you can define spamd_flags in rc.conf > I > just reinstalled 3.3.0 from source instead of ports Sounds like a bodge to me, and presumably it's using perl 5.8 because you replaced perl not because you installed SA manually. > and fixed the startup script, By the sound of it, your hacking the script was the only actual problem, so why repeat it. > so now it uses perl 5.8.9, yet it still seems to be > using a lot more CPU than 3.2.5 did...is this normal? > > load averages: 5.76, 5.19, 4.19 > > load averages: 3.20, 4.60, 4.15 By the look of it you are using way too many spamd children.