They do do damage as far as consumption of resources.
We had a server problem a week ago where for some reason Sniffer
stopped working. Tons of files built up then when Sniffer was
restarted we had lots of old artifact files.
CPU resources moved from single digit to 50-80% at times. After
deleting the old files, CPU went back to minimal status.
On Mar 8, 2007, at 11:30 AM, Colbeck, Andrew wrote:
I disagree.
Having MessageSniffer delete the old files would hide the problem.
With
the messages left behind, you have a valuable symptom that
something is
wrong with your infrastrucure.
If you ignore them, they are cosmetic and do not consume any disk
space
(relative to your normal disk space consumption of logging and spam
holding).
Andrew.
On Jul 14, 2006, at 2:23 PM, Pete McNeil wrote:
Hello Steve,
Normally these files should come and go quickly.
http://kb.armresearch.com/index.php?
title=Message_Sniffer.TechnicalDetails.Persistent
It's possible that when you reinstalled mxGuard something became
confused or improperly configured.
Stop processing messages.
Clean out any .QUE, .WRK, .XXX, .FIN, .ABT, and .LOCK files in the SNF
directory.
Regards,
Steve Guluk
SGDesign
(949) 661-9333
ICQ: 7230769
