On Wed, 2004-11-03 at 09:48 +1300, Jason Haar wrote: > Hi there > > I think the TCP option needs some more explicit documentation, as I have > begun seeing RPMs of clamav where the Socket option is *disabled* and the > TCP option is *enabled* as the defaults. > > As far as I'm aware, that is *not* a good idea. Not only are there now > network security issues you should attend to, but the TCP option IS ALWAYS > SLOWER THAN THE SOCKET MODE (please tell me if I am wrong). From what I can > gather, clamdscan has to pipe the entire file/directory to clamd over TCP - > whereas it only has to tell clamd where the file/dir is over Sockets.
I changed just recently to use UNIX socket mode a little over a month ago on the basis that TCP was deemed to be slower. Since changing, I have experienced many issues with runaway clamdscan processes and no noticeable performance increase. I process over a million mails a day using clamav with daemontools. I reverted back to tcp socket mode and have not had any issues so far (touch wood). my 2 cents worth... > > I don't think this difference is spelt out well enough if people are going > around making RPMs like that :-/ > > BTW: the RPM in question is clamd-0.80-1.1.fc2.dag - part of > http://apt.sw.be/fedora/ > > [I don't use it myself - just suffered the fallout...] > _______________________________________________ http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
