I have the opposite opinion with experience of using c-icap on freebsd. It was unstable and was almost not possible to debug problems. And I moved to squidclamav. I'm using 3.1.8 squid. It was about 4-5 month later, squid sometimes lose connection to c-icap, while c-icap was ok, icapclient says that c-icap working, but squid show error "icap timeout" or something like this. Only restarting c-icap AND squid solves that problem for some time. Than it happen again. I was tired of looking for problem in unreadable c-icap debug and no messages at all in squid logs about icap, just timeout, so I moved to squidclamav and it works pretty good! 2010/9/20 Henrik Nordström <henrik@xxxxxxxxxxxxxxxxxxx>: > mån 2010-09-20 klockan 19:28 +0200 skrev patrick.lanot@xxxxxxxxx: >> >> Hello >> >> First of all congratulations for your great work! >> >> I have one question for you please. >> >> I set up two squid proxy with WCCP (+squidclamav and squidguard)but I'm >> reinstalling all under 2 esxi vmware (vmware isn't the problem here).It >> would be better that I install the latest version 3.1.8 or version 2.7? >> version 3.1.8 of 20100920 it is a stable version? > > I would use 3.1.8. Allows you to replace squidclamav with c-icap + > clamav for a better virus scanning experience. > > Regards > Henrik > >
