On 2009-02-05 17:24, Madhuri Somavarapu wrote: > This is what I have in my clamd.conf on unix machine > > # Path to a local socket file the daemon will listen on. > # Default: disabled (must be specified by a user) > LocalSocket /tmp/clamd.socket > > # Remove stale socket after unclean shutdown. > # Default: yes > #FixStaleSocket yes > > # TCP port address. > # Default: no > #TCPSocket 3310 > > # TCP address. > # By default we bind to INADDR_ANY, probably not wise. > # Enable the following to provide some degree of protection > # from the outside world. > # Default: no > #TCPAddr 127.0.0.1 > > # Maximum length the queue of pending connections may grow to. > # Default: 15 > #MaxConnectionQueueLength 30 > > > Should I uncomment the line TCPSocket 3310.
Yes. > Is there any thing that admin has to do for the port number to be active. As far as clamav is concerned, no. However if you are connecting to clamd from a remote machine, and have a firewall, that might prevent the connection. > Also do I need to comment the line "LocalSocket /tmp/clamd.socket". > Not necessarily, you can have both a UNIX and TCP socket. > Is using the api right way to invoke the clamav > I never used the Java bindings. Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
