<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Glenn Steen wrote:
<blockquote
cite="mid:223f97700802200734n29031a3eg763c55dbddc1c09d@mail.gmail.com"
type="cite">
<pre wrap="">On 19/02/2008, Ugo Bellavance <a class="moz-txt-link-rfc2396E" href="mailto:ugob@lubik.ca"><ugob@lubik.ca></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">AlxFrag wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Glenn Steen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 15/02/2008, Martin.Hepworth <a class="moz-txt-link-rfc2396E" href="mailto:martinh@solidstatelogic.com"><martinh@solidstatelogic.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Also
The clamd facility is only really stable at 4.62 or later and didn't exist before 4.61..
</pre>
</blockquote>
<pre wrap="">Not to mention that no facility of MailScanner would ever run trhe
clamd _command_ ... Not whatsoever.
What seems to have happened here is that someone has followed a
bothced instruction on enabling clamdscan support by futzing the
clamav-* wrapper scripts. This of course hasn't worked, since clamd is
the server part, not the client.
This would explain the bogus log entries on both hosts.
What Alex should do is to follow the spirit of the wiki article
<a class="moz-txt-link-freetext" href="http://wiki.mailscanner.info/doku.php?id=documentation:anti_virus:clamav:switch_to_rpm_clamd">http://wiki.mailscanner.info/doku.php?id=documentation:anti_virus:clamav:switch_to_rpm_clamd</a>
to get things going on the newer install (4.66.5 was it?), and upgrade
the other one to a version later than 4.62.something (just as you say
Martin), and do the same there.
Only other really viable option would be to run clamavmodule on the old one.
Cheers
</pre>
</blockquote>
<pre wrap="">Good morning,
I've followed your advice and these described in
<a class="moz-txt-link-freetext" href="http://wiki.mailscanner.info/doku.php?id=documentation:anti_virus:clamav:switch_to_rpm_clamd">http://wiki.mailscanner.info/doku.php?id=documentation:anti_virus:clamav:switch_to_rpm_clamd</a>.
I've also modified the clamav-wrapper file to its original form.
Now, no warnings are displayed. The problem is that clamscan is running
that needs too much CPU.
How can i switch to clamdscan?
</pre>
</blockquote>
<pre wrap="">- make sure you're running a version of MS that supports clamd
- make appropriate changes in MailScanner.conf
- restart MailScanner
Ugo
</pre>
</blockquote>
<pre wrap=""><!---->If the version is too old for clamd (4.62.something...?), then use clamavmodule.
Cheers
</pre>
</blockquote>
i've solved the problem thanks! the only thing i had to specify is
Virus Scanners = clamd instead of Virus Scanners = clamav.<br>
<br>
<br>
Alex<br>
</body>
</html>