On Thu, 10 May 2007 12:39:51 +0100, Nigel Frankcom <[EMAIL PROTECTED]> wrote:
>On Thu, 10 May 2007 12:28:31 +0100, Nigel Frankcom ><[EMAIL PROTECTED]> wrote: > >>On Thu, 10 May 2007 12:01:53 +0100, Nigel Frankcom >><[EMAIL PROTECTED]> wrote: >> >>>Hi All, >>> >>>I saw the mention earlier about spamd logs and thought I'd check mine. >>>In 12 hours it has achieved the impressive, if very worrying size of >>>1.8 Gb. A check back over the last few days show similarly sized logs. >>> >>>My system lint's clean. and sa-compile ran fine after I removed the >>>rules that were throwing an error (and mucked about getting ImageInfo >>>working without erroring). >>> >>>Will dropping the -s /var/log/spamd.log from /init.d/spamassassin stop >>>logging? I know that's not an ideal solution but it's certainly >>>preferable to multi Gb log files. >>> >>>This isn't going to kill my hdd or fill it, but it's certainly not >>>going to be helping matters. >>> >> >> >>It seems spamd -s null in the init.d will stop logging >>(http://spamassassin.apache.org/full/3.2.x/doc/spamd.html) but, even >>if the rules are erroring, are they actually doing anything to catch >>spam? Is it better to remove the rules or kill the logging? >> > >Correction: The change I've made to disable logging is in >/etc/sysconfig/spamassassin > >It seems to have stopped the logging at least, I'm unsure of what >other problems it may create. Duh me! - Perl was 5.8.5 (coulda sworn I updated it but apparently not). On CentOS enabling centosplus in the yum config allowed me to update Perl to 5.8.8. It seems to have gone in without a hitch and logs don't seem to be running away now. That said I did move out some of the rules that were apparently causing a problem. HTH someone else. KR Nigel
