Also, I agree with Paul that a rule-base should not be rolled into production if it is corrupted. My issue, even with a successful manual download, is that the rule-base cannot be replaced because it is in use:
===== New File Tested GOOD! The process cannot access the file because it is being used by another process. A duplicate file name exists, or the file cannot be found. =====
The existing rule-base file cannot be renamed because it is in use, thus the new rule-base file rename fails and disappears because of the final delete statement in the autosnf.cmd file. Any better way to handle the migration of new rule-base files into a busy Sniffer environment?
When running 2-3 the rulebase file will not be touched for minutes at a time so this problem should be reduced significantly.
Prior to 2-3 the rulebase file would be loaded very frequently.
2-3 is currently a beta but it has been extremely stable.
_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
