http://bugzilla.spamassassin.org/show_bug.cgi?id=4309
------- Additional Comments From [EMAIL PROTECTED] 2005-05-06 19:33 -------
Subject: Re: Spamc/d should log memory and message-id after processing
> I think the idea is to log the Message-ID on errors and warns, too.
> that way the log that now contains:
>
> In other words, attach the message-id to every error message.
That might be a good idea, but it wasn't what I had originally suggested.
My proginal suggestion was for a new log entry that said something like
(format it as you will):
Spamd pid 1234: 14:32:51 Processed message <> ram <nn>.
If you want to add in a processing time for the message, that would be a
bonus.
If you want to combine the memory report with an existing "completed
processing" message, that would be fine, AS LONG as the report shows up in
the same format for all messages, no matter how the processing turned out.
And AS LONG as the memory report also appears on bayes/awl update
completions.
The idea is simply to track spamd memory usage per message, also showing the
message processing sequence, on the assumption that memory growth is related
more to the sequence than to an individual message.
Note: It now occurs to me that since spamd can get aborted, it might make
sense to report "started processing message <> ram nn", so that a log entry
will show up even if a message aborts. In this case you obviously wouldn't
need a message at the end of processing, since the previous message
presumably ended with the amount of ram this one is starting at.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
