On Sunday, October 31, 2004, 9:45:19 PM, Andrew wrote: CA> For what it's worth, another two lessons I learned:
CA> If you start a persistent instance, then delete or rename your rulebase, CA> when you issue a reload, you get this in your log: CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> snfrv2r3 20041031022545 -INITIALIZING- 0 0 ERROR_RULE_FILE 67 CA> I also learned that if you don't notice it for a day, you can slow your mail CA> server down by letting sniffer append new log lines to an ever-growing 800+ CA> MB text file! Is this condition cleared after a proper rulebase file is in place again? Please clarify so that I can look into this. Thanks, _M This E-Mail came from the Message Sniffer mailing list. For information and (un)subscription instructions go to http://www.sortmonster.com/MessageSniffer/Help/Help.html
