I want cleaner logs. This has been discussed in the list before, and I'm
pretty sure that Pete and Sandy agreed that they'd seen the behaviour
elsewhere, i.e. that multiple processes of writing to the same log file are
garbling the text file, and that per se, the garbling wasn't strictly
Andrew,
I just wanted to chime in and say that I of course would love to see
non-text base64 stuff thrown out before scanning, and allow us to target
only unencoded text strings. The idea of scanning only the decoded text
would also be a big processor saver and the primary method, so maybe
;)
-Original Message-
From: Colbeck, Andrew
Sent: Monday, February 23, 2004 12:58 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [Declude.JunkMail] Feature-itis
Matt, it's not that I particularly want the log files to be neatly ordered
instead of interleaved. Although it would be nice, I'm used
PROTECTED] On Behalf Of Matt
Sent: Monday, February 23, 2004 3:29 PM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Feature-itis
Ick :)
LOGLEVEL MID doesn't look nearly as bad, though there will be the
occasional series of line breaks with code appearing in it. I haven't
tried parsing
Just a thought, Scott, you already send log info to Declude Console, how
about using Declude console or some other helper app as the log writer,
keeps the conversation local and should resolve the whole two processes
write to the same line issue?
The problem is that the code used to communicate
However, it may not be very easy to integrate syslogging
support into Declude. I am curious to know if the majoriety
of folks would prefer that the focus of the developer(s) be
maintained on developing new spam features versus re-tooling
Declude to work with a syslog daemon. Depending
- Original Message -
From: Markus Gufler [EMAIL PROTECTED]
However, it may not be very easy to integrate syslogging
support into Declude. I am curious to know if the majoriety
of folks would prefer that the focus of the developer(s) be
maintained on developing new spam features
