I'm trying to build 0.103.0 on a CentOS6 server and the build completes
but the 'make check' is giving a failure on check3_clamd.sh. The file
unit_tests/check3_clamd.log contains the following but apart from the
obvious that the reply is the wrong size I don't know what this is
telling me or
Shawn Webb wrote:
On Wed, Sep 25, 2013 at 4:51 AM, Francis Stevens
francis.stev...@bristow.co.uk wrote:
Shawn Webb wrote:
On Tue, Sep 24, 2013 at 2:21 PM, Rob Sterenborg (lists)
li...@sterenborg.info wrote:
On 09/24/2013 03:51 PM, Shawn Webb wrote:
On Mon, Sep 23, 2013 at 5:04 PM
Shawn Webb wrote:
On Tue, Sep 24, 2013 at 2:21 PM, Rob Sterenborg (lists)
li...@sterenborg.info wrote:
On 09/24/2013 03:51 PM, Shawn Webb wrote:
On Mon, Sep 23, 2013 at 5:04 PM, Dennis Peterson denni...@inetnw.com
wrote:
On 9/23/13 1:59:42PM, Shawn Webb wrote:
Maybe this time I'll
I have also hit this compilation issue, also on an old RedHat system.
Looking in the sources for the file libclamav/7z/Types.h for 0.97.8
there are some edits that seem to be working around this issue which
don't appear in the corresponding Types.h file for 0.98. The diff
output is a bit long
Shawn Webb wrote:
On Mon, Sep 23, 2013 at 10:33 AM, Francis Stevens
francis.stev...@bristow.co.uk wrote:
I have also hit this compilation issue, also on an old RedHat system.
Looking in the sources for the file libclamav/7z/Types.h for 0.97.8 there
are some edits that seem to be working
I've tried a build on an ancient RedHat system and the make seems to
complete ok but a make check fails with:
make[2]: Entering directory `/test/email/clamav-devel/unit_tests'
CC check_clamav-check_clamav.o
CC check_clamav-check_jsnorm.o
CC check_clamav-check_str.o
CC
I should have said that the build seems to work fine, it's only the
check that is having problems.
FAS
Francis Stevens wrote:
I've tried a build on an ancient RedHat system and the make seems to
complete ok but a make check fails with:
make[2]: Entering directory `/test/email/clamav-devel
Thanks for that, I've pulled down the latest version but still see the
same error with make check.
FAS
Török Edwin wrote:
On Tue, 23 Nov 2010 10:32:02 +
Francis Stevensfrancis.stev...@bristow.co.uk wrote:
I've tried a build on an ancient RedHat system and the make seems
to complete ok
ancient... 2.2.4
Török Edwin wrote:
On Tue, 23 Nov 2010 12:17:02 +
Francis Stevensfrancis.stev...@bristow.co.uk wrote:
Thanks for that, I've pulled down the latest version but still see
the same error with make check.
And your glibc version is?
--Edwin
That fixed it!! Thanks for taking time to look into this for such an
old system (and sysadmin come to that :-))
FAS
Török Edwin wrote:
On Tue, 23 Nov 2010 14:14:30 +
Francis Stevensfrancis.stev...@bristow.co.uk wrote:
ancient... 2.2.4
OK, I set the ifdef to 2.3 (looks like it got
Chris wrote:
I've misplaced the original post I made so I can't reply to it, however
I'd like to make a note for the archives what the problem is and to
thank Steve Basford and Edwin for the their help in finding it. Seems
like I had both a main.cvd and main.cld. I removed the main.cld file and
Leonardo Rodrigues wrote:
Em 16/04/2010 07:22, Török Edwin escreveu:
On 04/16/2010 01:07 PM, Dima wrote:
I have something very much doubt that this can be done on the old
compiler
using libraries of those times.
People have successfully built ClamAV on various old systems, maybe
not with
Simon Hobson wrote:
And then of course, there's an element of which language ?
It's one thing if I can just hit make clean ; make and it all works - but
when it doesn't - then being able to at least read whatever language is kinda useful. I
do have some programming experience (done Pascal
I'm trying to install 0.95.3 on a RedHat system currently running 0.95.2
and am getting the following error from make install
make[4]: Entering directory `/root/email/clamav-0.95.3/libclamav'
test -z /usr/local/lib/ || /bin/mkdir -p /usr/local/lib/
/bin/sh ../libtool --mode=install
, is it this bundling that is causing the
problem? If only I understood advanced Makefiles I might stand a chance
of making this change...
FAS
Francis Stevens wrote:
I'm trying to install 0.95.3 on a RedHat system currently running 0.95.2
and am getting the following error from make install
individually, is it this bundling that is causing the
problem? If only I understood advanced Makefiles I might stand a chance
of making this change...
FAS
Francis Stevens wrote:
I'm trying to install 0.95.3 on a RedHat system currently running
0.95.2 and am getting the following error from make
Török Edwin wrote:
On 2009-10-29 12:42, Francis Stevens wrote:
I'm trying to install 0.95.3 on a RedHat system currently running
0.95.2 and am getting the following error from make install
Which RedHat version, is it a RHEL?
It's an old system based on Redhat 7.2 but with a new kernel
Rick,
Thank's for that, it has fixed my install problem. Will you raise the
bug report or should I?
FAS
Rick Cooper wrote:
Original Message
From: clamav-users-boun...@lists.clamav.net
[mailto:clamav-users-boun...@lists.clamav.net] On Behalf Of Francis Stevens
Sent: Thursday, October
Bug #1738 raised.
FAS
Török Edwin wrote:
On 2009-10-29 15:37, Rick Cooper wrote:
Original Message
From: clamav-users-boun...@lists.clamav.net
[mailto:clamav-users-boun...@lists.clamav.net] On Behalf Of Francis Stevens
Sent: Thursday, October 29, 2009 6:43 AM To: ClamAV users ML
I have been having the same problem and was even more puzzled when
scanning the rogue file on my test system didn't exhibit the same
problem (it scanned in a fraction of a second as against over a minute
on my production system). The reason for the difference was that in
/etc/clamd.conf on my
Doug Hardie wrote:
I have been running clamav for quite some time now. For most of that
time I was receiving between 1500 and 2000 viruses per day. However,
lately the number is down to about 200 per day. I don't have any users
complaining about receiving viruses so I don't think there is a
I'm seeing several false positives for Exploit.W32.MS05-002 since I
upgraded to 0.82 yesterday. I've posted samples to the submission
website but would like to do something about this. Using sigtool -l
doesn't list Exploit.W32.MS05-002 as a signature in the database, is
there any way I can
Francis Stevens wrote:
I'm seeing several false positives for Exploit.W32.MS05-002 since I
upgraded to 0.82 yesterday. I've posted samples to the submission
website but would like to do something about this. Using sigtool -l
doesn't list Exploit.W32.MS05-002 as a signature in the database
Ralf Hildebrandt wrote:
* Francis Stevens [EMAIL PROTECTED]:
Finally worked out how to (correctly) revert to 0.81, had to remove the
libraries in /usr/local/lib before doing the make install for 0.81.
I'm no longer getting the false positives, just the WARNING message from
freshclam - which
Trog wrote:
You can apply the enclosed patch if you want less stringent checking.
Tried the patch and it fixes the problem for all the false positives
I've seen so far, so it looks good to me. Will this make it into 0.83?
Thanks for the rapid response.
FAS
Trog wrote:
BTW, all the false positives I've seen so far are also reported as
broken by the showriff utility, which was written specifically to check
these files.
For example:
$ showriff virus-2005-02-08-n0009134
Contents of file virus-2005-02-08-n0009134 (18926/0x8926 bytes):
All the problem
Since I upgraded to 0.80 I am seeing many false positives for the
Oversized.zip virus, I have posted samples at the ClamAV website but in
the mean time is there a way of removing the signatures for this virus
from my copy of the database?
FAS
___
Whenever a file exceeds ArchiveMaxCompressionRatio (see clamd.conf man page), it's considered a logic bomb and marked as Oversized.zip . Try increasing your ArchiveMaxCompressionRatio setting.
Francis Stevens wrote:
Since I upgraded to 0.80 I am seeing many false positives
. Anyone know whay ArchiveMaxCompressionRatio doesn't work and
what I can do about it?
FAS
Francis Stevens wrote:
If only I'd waited a bit longer... I now find the answer to my own
question in the FAQ (should have looked first... a case of engaging the
maillist before the brain... sorry). I post
So I'm slightly stupid... I now know that clamscan doesn't seem to read
the options in /etc/clamd.conf but clamdscan does (or rather clamd
does), but of course you have to restart clamd after changing a value.
Obviously must try harder as they used to say at school.
FAS
Francis Stevens wrote:
I
I've just upgraded to clamav 0.75 and as a result of running my
testsuite I've found that clamscan no longer detects the W32.Magistr.A
virus. This seems to be an issue with the signature database (I run
freshclam from cron) as when I put back a copy of the signature database
from a couple of
31 matches
Mail list logo
