> Forgive me if I'm naive, but what does a local virus scanner have to > do with TCP/IP?
I'll write how I understand it. In the case being discussed we have ClamD running as a service under Windows. When clamdscan is called to actually scan a file then that instance of clamdscan communicates with ClamD which is already resident. Because ClamD is running and listening then this makes the scanning process faster since some functions are already in memory awaiting service. But in order for this to occur ClamD has to be "listening" for a request from the calling program. Normally the service establishes a socket - meaning a hole punched through the OS - to allow such communication to occur. However, for ClamD in the configuration file there is an option to bind the service to a specific IP address and a specific port assignment. For greater security 127.0.0.1 is the default address. But the service could be bound to another IP address. I don't know why this might solve "stability problems" on some versions of windows but that's the message in the conf and somethng I was advised to try from my forum posting. Since the error I was seeing in the ClamD log file was an error with accept() it seemed reasonable to me to try it. --- This E-mail came from the Declude.Virus mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.Virus". The archives can be found at http://www.mail-archive.com.
