Hello Pi-Web,

Saturday, February 2, 2008, 6:07:19 PM, you wrote:

> Hi Pete,

> Just for information, we renamed the msg folder again today, and again

> "SNFClient.exe.err only state: Could Not Connect!"

> "/etc/init.d/snfilter stop" + "/etc/init.d/snfilter start" helped.

When SNFClient cannot connect the SNFServer is either not accepting
new connections, or it is down.

If it is down then restarting it helps by starting it again.

If it is not down then restarting helps by abandoning all of the
existing connections -- many of them will re-try and succeed when the
SNFServer is active again.

This "stalling" effect is seen only when you rename the folder that
contains the message files --

I wonder if there is a quirk of the environment that causes the
SNFServer engine to be hung attempting to open and/or read the files
in the changed directory such that additional scan requests queue up
and are not serviced.

Since SNFServer is not giving any errors (or at least you're not
reporting any so it is likely that it is not) then I can only assume
the program has not seen any errors that it can report.

It is probably not a good idea to rename the folder while there is any
possibility of active scans in progress.

Instead I would suggest that you create a new folder with the correct
name for new scans (perhaps by date) and then abandon the older folder
in place. New scans would be done in the new folder and old or
existing scans would continue in the old folder until they were
complete. By the time you do anything with the old folder it will be
several generations behind and safe.

I do not completely understand your methodology -- but if I'm correct
about it then the above approach should work.

I might also recommend a different approach --

Use a single directory for scans and have them always performed there.
Then - depending upon the scan result move them into the appropriate
directory. This way you could always be assured that the scanner is
finished with a file before it is ever moved. This is an efficient
process on ext3 and most other modern *nix file systems since it only
requires the adjustment of a node and that operation will itself be
journalized first.

Thanks for keeping us posted.

Hope this helps,

_M

-- 
Pete McNeil
Chief Scientist,
Arm Research Labs, LLC.


#############################################################
This message is sent to you because you are subscribed to
  the mailing list <sniffer@sortmonster.com>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to  <[EMAIL PROTECTED]>

Reply via email to