You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by ji...@jidanni.org on 2007/10/19 08:01:25 UTC
Check $HOME for an ever growing razor-agent.log
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-agent.log && ln -s /dev/null razor-agent.log ?
Re: Check $HOME for an ever growing razor-agent.log
Posted by Bill Landry <bi...@inetmsg.com>.
jidanni@jidanni.org 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 spamassassin, logging
> should be off by default? Docs not clear.
>
> Or must one rm razor-agent.log && ln -s /dev/null razor-agent.log ?
>
I'm not sure how an sa-update could have anything to do with razor
logging, since it is controlled via the "debuglevel" setting in your
razor-agent.conf file. See "man razor-agent.conf" for info.
Bill
Re: Check $HOME for an ever growing razor-agent.log
Posted by ji...@jidanni.org.
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.
Re: Check $HOME for an ever growing razor-agent.log
Posted by "John D. Hardin" <jh...@impsec.org>.
On Sat, 20 Oct 2007 jidanni@jidanni.org 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 directory:
> $ ls -ogt .razor
> -rw------- 1 854 2007-10-20 09:01 server.c104.cloudmark.com.conf
> -rw------- 1 38 2007-10-20 09:01 servers.catalogue.lst
> -rw------- 1 38 2007-10-20 09:01 servers.nomination.lst
> -rw------- 1 854 2007-10-20 08:20 server.c103.cloudmark.com.conf
> -rw------- 1 0 2007-10-20 07:59 razor-agent.log
> -rw------- 1 14 2007-10-20 07:59 servers.discovery.lst
> -rw-r--r-- 1 13 2007-10-20 07:56 razor-agent.conf
The logfile is zero size.
> To much excitement for me. It just loves writing various files
> apparently. Instead I now just did:
> cd && ln -s /dev/null razor-agent.log && rm -r .razor
Why not let it run for a bit with the new settings and see whether
debuglevel=0 is indeed suppressing logging before you do something as
drastic as linking the logfile to /dev/null?
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
...the Fates notice those who buy chainsaws...
-- www.darwinawards.com
-----------------------------------------------------------------------
10 days until Halloween
RE: Check $HOME for an ever growing razor-agent.log
Posted by Michael Scheidell <sc...@secnap.net>.
> -----Original Message-----
> From: jidanni@jidanni.org [mailto:jidanni@jidanni.org]
> 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.c103.cloudmark.com.conf
> -rw------- 1 0 2007-10-20 07:59 razor-agent.log
> -rw------- 1 14 2007-10-20 07:59 servers.discovery.lst
> -rw-r--r-- 1 13 2007-10-20 07:56 razor-agent.conf
>
> To much excitement for me. It just loves writing various
> files apparently. Instead I now just did: cd && ln -s
> /dev/null razor-agent.log && rm -r .razor
>
Good, then everytime you start razor instead of reading a few bytes from
your hard disk, it will need to flood the cloudmark network looking for
reachable servers.
Soon you won't have to worry abour razor, since they will blacklist you.
_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(tm).
For Information please see http://www.spammertrap.com
_________________________________________________________________________
Re: Check $HOME for an ever growing razor-agent.log
Posted by ji...@jidanni.org.
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 server.c104.cloudmark.com.conf
-rw------- 1 38 2007-10-20 09:01 servers.catalogue.lst
-rw------- 1 38 2007-10-20 09:01 servers.nomination.lst
-rw------- 1 854 2007-10-20 08:20 server.c103.cloudmark.com.conf
-rw------- 1 0 2007-10-20 07:59 razor-agent.log
-rw------- 1 14 2007-10-20 07:59 servers.discovery.lst
-rw-r--r-- 1 13 2007-10-20 07:56 razor-agent.conf
To much excitement for me. It just loves writing various files
apparently. Instead I now just did:
cd && ln -s /dev/null razor-agent.log && rm -r .razor
Re: Check $HOME for an ever growing razor-agent.log
Posted by Theo Van Dinter <fe...@apache.org>.
On Fri, Oct 19, 2007 at 02:01:25PM +0800, jidanni@jidanni.org 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're now using
the Razor plugin (which sa-update can't change either unless you let it
enable plugins that come from the update channel) for checks or reports,
and haven't disabled razor logging, then sure, you'll get a log.
> How to tell it that just like the other 99% of spamassassin, logging
> should be off by default? Docs not clear.
Razor is not SpamAssassin, it's a third-party tool that can be used by
SpamAssassin. :) If you don't want logging in razor, it's trivial to
turn it off.
> Or must one rm razor-agent.log && ln -s /dev/null razor-agent.log ?
You could read the docs to find out how to disable it. :)
In short, add the following to your ~/.razor/razor-agent.conf file:
debuglevel = 0
--
Randomly Selected Tagline:
"... charges of the negative persuasion ..." - Prof. Demetry