YES you're right. Thank you for your good idea.
It is because I don't have the full path in the file that clamd can't
find it.
I wonder why vscan-clamav does like that now.
Maybe changes in samba security ?
I can't see any way to put this option in smb.conf or vscan-clamav.conf.
I'm going to s
On 04/15/2010 05:19 PM, Philippe Camps wrote:
I reboot the server with the new kernel, and then rebuild the
vscan-clamav.so module and upgrade clamav.0.95.3 to clamav.0.96.
I have no errors when I start clamav.
I put the debug yes in clamd.conf.
I put a file test.txt in my samba share folder, an
April 2010 15:19
To: clamav-users@lists.clamav.net
Subject: Re: [Clamav-users] vscan-clamav samba with new redHat 5.5
I reboot the server with the new kernel, and then rebuild the vscan-clamav.so
module and upgrade clamav.0.95.3 to clamav.0.96.
I have no errors when I start clamav.
I put th
I reboot the server with the new kernel, and then rebuild the
vscan-clamav.so module and upgrade clamav.0.95.3 to clamav.0.96.
I have no errors when I start clamav.
I put the debug yes in clamd.conf.
I put a file test.txt in my samba share folder, and I notice always the
same error:
/Apr 15 1
Hi,
I use samba-vscan 0.3.6c with samba-3.0.33-3.15.el5 on Red Hat 5.4.
Everything was working fine until the new update to Red Hat 5.5.
I have now samba-3.0.33-3.28.el5 and glibc-2.5-49.
I have messages errors when I try to access a file with samba:
Apr 2 13:46:26 spinel smbd_vscan-clamav[2031
