Your best bet is to ask on the ClamWin forum. Here is the forum site
http://forums.clamwin.com/
I'm not sure if he's talking about the binaries here, auto-built by
ClamAV Team (not the version by the ClamWin team)
http://sourceforge.net/projects/clamav/files/clamav/win32/
The builds used to
On 25 Jun 2012 at 8:13, Steve Basford wrote:
Your best bet is to ask on the ClamWin forum. Here is the forum site
http://forums.clamwin.com/
I'm not sure if he's talking about the binaries here, auto-built by
ClamAV Team (not the version by the ClamWin team)
Den 2012-06-24 09:31, Frank Chan skrev:
I did check again and it appears that it that clamav-0.97.4 was
installed in /usr/local/bin rather than the normal /usr/bin that I
selected so when I did a freshclam the path /usr/local/bin was before
/usr/bin so it saw the older version.
this is so
Den 2012-06-24 16:41, Dennis Peterson skrev:
On 6/24/12 7:37 AM, David Alix wrote:
which version of clamd are you running?
9.7.2, 9.7.4, and 9.7.5.
all at once to be sure ?
___
Help us build a comprehensive ClamAV guide: visit
On Mon, Jun 25, 2012 at 08:13:58AM +0100, Steve Basford wrote:
While I can see the MSI installer being useful to some people... I'd
prefer to have the .ZIPs back (or have both built), as I've got to run the
MSI
installer, find where the files have been installed and them copy them out,
so I
On Mon, Jun 25, 2012 at 08:13:58AM +0100, Steve Basford wrote:
While I can see the MSI installer being useful to some people... I'd
prefer to have the .ZIPs back (or have both built), as I've got to run
the
MSI
installer, find where the files have been installed and them copy them
out,
so
On 6/25/12 12:41 AM, Benny Pedersen wrote:
Den 2012-06-24 16:41, Dennis Peterson skrev:
On 6/24/12 7:37 AM, David Alix wrote:
which version of clamd are you running?
9.7.2, 9.7.4, and 9.7.5.
all at once to be sure ?
No - I have several systems around the world running ClamAV, each running
Hello,
I am administering a Red Hat Enterprise 5 server and was running ClamAV 97.3
and upgraded to version 97.5. Prior to upgrading I removed the earlier Clam RPM
completely.
The issues I'm having are as follows:
The ClamAV installation on red hat is producing the following error when we run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mario,
On 25/06/2012 09:15, mario.reyes@dot.gov wrote:
Hello,
I am administering a Red Hat Enterprise 5 server and was running
ClamAV 97.3 and upgraded to version 97.5. Prior to upgrading I
removed the earlier Clam RPM completely.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/06/2012 00:14, David Alix wrote:
Hello- Since Thursday morning, sometime between the daily.cld
15065 and 15066 update, my clamd daemon has been abending regularly
(every couple of minutes to every half hour). I am running clamd
0.97.2 on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paul,
On 24/06/2012 18:15, Paul Whelan wrote:
What's the reason for the change in the packaging of the windows
binaries?
The windows binaries where packaged with custom shell script before,
now they are packaged by VisualStudio when we build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/06/2012 04:34, Steve Basford wrote:
On Mon, Jun 25, 2012 at 08:13:58AM +0100, Steve Basford wrote:
While I can see the MSI installer being useful to some
people... I'd prefer to have the .ZIPs back (or have both
built), as I've got to run
On 06/25/12 15:55, Tom Judge wrote:
Exclusion of the necessary msvc* runtime libraries
The inclusion of them helps lower the barrier to entry for people to
try ClamAV on windows.
So why have you removed them?
Inclusion of the previously separate libclamunrar libs
There is no reason for
Hey Tom,
Thanks for the suggestion but it just gives me the same message over and over
that I find in the log.
ClamAV update process started at Mon Jun 25 09:55:43 2012
WARNING: Can't query current.cvd.clamav.net
WARNING: Invalid DNS reply. Falling back to HTTP mode.
Reading CVD header
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/06/2012 10:10, aCaB wrote:
On 06/25/12 15:55, Tom Judge wrote:
Exclusion of the necessary msvc* runtime libraries
The inclusion of them helps lower the barrier to entry for
people to try ClamAV on windows.
So why have you removed them?
On 6/25/12 7:00 AM, mario.reyes@dot.gov wrote:
Hey Tom,
Thanks for the suggestion but it just gives me the same message over and over
that I find in the log.
ClamAV update process started at Mon Jun 25 09:55:43 2012
WARNING: Can't query current.cvd.clamav.net
WARNING: Invalid DNS reply.
On 06/25/2012 05:26 PM, Tom Judge wrote:
On 25/06/2012 10:10, aCaB wrote:
FYI unrar license is incompatible with the GPL. That was the
rationale in the packaging.
Yes that is why they are separate binaries. As far as we can tell
there is nothing that states that you can't put them in
You may be up against a limitation of your BIND resolver. - First thought
was a DNS issue but according to the FAQ's on Clam site, it should resolve
using TXT format, which it does successfully. Unfortunately at this site I'm
not in charge of the DNS servers.
How would I resolve a limitation
Truss isn't installed on this server, nor can I make any changes to the
baseline...
Do you think it could be a firewall issue somewhere? I can resolve manually
db.local.clamav.net just no way to get a resolution on current.cvd.clamav.net?
Can I replace that DNS server with a local one?
On 6/25/12 7:52 AM, mario.reyes@dot.gov wrote:
Truss isn't installed on this server, nor can I make any changes to the
baseline...
Do you think it could be a firewall issue somewhere? I can resolve manually
db.local.clamav.net just no way to get a resolution on current.cvd.clamav.net?
VisualStudio does not have a target to build a ZIP file, we could also
build a cab file if this would help.
Hi Tom,
Any use?
http://markkemper1.blogspot.co.uk/2010/10/zipping-build-outputs-using-build-file.html
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 22/06/2012 17:56, Reynolds, David C. wrote:
This is a resend from about 2 weeks ago for which there was no
reply. Any help is appreciated
Sorry for the late response.
...
Resolved!
The issue was hard permission on /etc/resolv.conf - it was 600 and I changed it
to 644 and it was able to execute with no problem
Appreciate the fast responses and assistance!!!
V/R
Mario Reyes
-Original Message-
From: clamav-users-boun...@lists.clamav.net
On 25 Jun 2012 at 9:55, Tom Judge wrote:
Hi Paul,
On 24/06/2012 18:15, Paul Whelan wrote:
What's the reason for the change in the packaging of the windows
binaries?
The windows binaries where packaged with custom shell script before,
now they are packaged by VisualStudio when we
24 matches
Mail list logo
