JDH> Why not let it run for a bit with the new settings and see whether
JDH> debuglevel=0 is indeed suppressing logging before you do something as
JDH> drastic as linking the logfile to /dev/null?
Yes you are right. .razor/* though changing often, at least aren't growing.
On Sat, 20 Oct 2007 [EMAIL PROTECTED] wrote:
> TVD> In short, add the following to your ~/.razor/razor-agent.conf file:
> TVD> debuglevel = 0
>
> OK, I did mkdir .razor && echo debuglevel=0 > .razor/razor-agent.conf
> That was at 7:56. Now the activity has shifted to that new director
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 19, 2007 9:16 PM
> To: users@spamassassin.apache.org
> Subject: Re: Check $HOME for an ever growing razor-agent.log
>
>
> -rw--- 1 854 2007-10-20 08:20 server
TVD> In short, add the following to your ~/.razor/razor-agent.conf file:
TVD> debuglevel = 0
OK, I did mkdir .razor && echo debuglevel=0 > .razor/razor-agent.conf
That was at 7:56. Now the activity has shifted to that new directory:
$ ls -ogt .razor
-rw--- 1 854 2007-10-20 09:01 s
[EMAIL PROTECTED] wrote the following on 10/18/2007 11:01 PM -0800:
> Check your $HOME for an ever growing ~/razor-agent.log apparently
> brought in by sa-update two days ago, which will one day fill your
> disk, according to a web search.
>
> How to tell it that just like the other 99% of spamassa
On Fri, Oct 19, 2007 at 02:01:25PM +0800, [EMAIL PROTECTED] wrote:
> Check your $HOME for an ever growing ~/razor-agent.log apparently
> brought in by sa-update two days ago, which will one day fill your
> disk, according to a web search.
sa-update doesn't impact the razor config at all. If you'r
Check your $HOME for an ever growing ~/razor-agent.log apparently
brought in by sa-update two days ago, which will one day fill your
disk, according to a web search.
How to tell it that just like the other 99% of spamassassin, logging
should be off by default? Docs not clear.
Or must one rm razor
