I have come a long way.... I finally managed to install everything even though
I got many compilation problems when building c-icap. If useful to anyone, when
compiling c-icap, you also have to download and compile the icap modules in
order to get support for clamav. Also blastwave repositories don't have the
latest clamav-0.97. You can find that version in openCSW repositories.
BUT.... now I have a problem I can't read files on the dataset where vscan is
enabled, but I can create new files. I disable it and then everything works
fine again. I killed the c-icap server and left vscan on to see if it had to do
with c-icap and it behaves the same way.
Apparently vscan is failing to communicate with the c-icap server. When I run
"vscanadm stats" I get:
scanned=0
infected=0
failed=31
I understand that c-icap communicates with clam_av using a service declared in
c-icap.conf. To add an engine I followed the steps:
# ./vscanadm add-engine motor1 (I picked this name randomly, it doesn't match
anything in the system)
# ./vscanadm set-engine -p host=localhost motor1
# ./vscanadm show to see the details of the engine that was created:
What I don't get is how vscan knows how to communicate with the c-icap server.
Maybe here lies the problem...
Any ideas?
--
This message posted from opensolaris.org
_______________________________________________
distribution-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/distribution-discuss
