Sorry, but it didnt help.
Hello Walter,
Friday, March 16, 2007, 6:21:39 PM, you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sergio,
do you have libgmp on your system ?
If yes, do the following:
setenv CFLAGS -O2 -I/usr/local/include
setenv LDFLAGS -s -L/usr/local/lib
And, I found that I dont have libthread library on my server. Maybe,
this is my problem.
But if thats right, I dont know how to install this library to my
pc...
Hello Walter,
Friday, March 16, 2007, 6:21:39 PM, you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sergio,
do you have
Hi everyone,
My clamava seems to be disconnecting quite often- and my paniclog is full of
timed out entries-
how can I get the clamlog to give me more detail- and timestamp the entries-
here's a portion of my clamlog
/var/spool/exim/scan/1HTHbI-0003XF-LE/1HTHbI-0003XF-LE.eml:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sergio,
I assume you mean 'libpthread' instead of 'libthread'.
Please try this:
# ./configure --sysconfdir=/etc --disable-pthreads --with-user=amavis
- --with-group=amavis --enable-experimental
Please substitute --with-user= and --with-group=
Robert wrote:
It's only happened the once. By the time I inspected the
/usr/local/share/clamav
directory there was no sign of a .dbLock file.
However, the database directory is definitely writable by clamd.
It's owned by the clamav user.
Since the restart of clamd it has been behaving
On Sat, Mar 10, 2007 at 11:38:47AM +0100, Jan-Pieter Cornet wrote:
On Sat, Mar 10, 2007 at 11:26:10AM +0100, Marc Haber wrote:
On Sat, Mar 10, 2007 at 11:11:39AM +0100, Jan-Pieter Cornet wrote:
Just put this in your freshclam.conf:
ScriptedUpdates no
It will make sure only .cvd
Hi Everyone,
I'm new to this list, but a long time user of ClamAV.
For years I've been using this simple procmail (clamscan-procfilter.pl)
script from
http://www.virtualblueness.net/~blueness/clamscan-procfilter/
It's worked great, until I upgraded to the 0.9X ClamAV and it no longer
is able
Michael Brown wrote:
Hi Everyone,
I'm new to this list, but a long time user of ClamAV.
For years I've been using this simple procmail (clamscan-procfilter.pl)
script from
http://www.virtualblueness.net/~blueness/clamscan-procfilter/
It's worked great, until I upgraded to the 0.9X ClamAV and
Jim Maul wrote:
Im not running 0.9X but im pretty sure --mbox isnt valid anymore. And
why is the variable CLAMSCAN when its calling clamDscan? Its just a
little confusing...
Wow, you guys are amazing, that's exactly what it was! I removed the
--mbox and everything works again!!
The
