I've inherited a box with a wildly non-standard install (Mac OS X.3 server).
How do I track down where the old stuff is to uninstall it?
Thanks,
Davis
From: James [EMAIL PROTECTED]
Reply-To: ClamAV users ML [EMAIL PROTECTED]
Date: Tue, 14 Dec 2004 10:02:22 -0600
To: ClamAV users ML [EMAIL
Thank you for yor answer, Nigel. I am using Mandrake Community 10.1
What is 'clamscand'?
To be honest, I don't know. I'm just triyint to make clamav works
in deamon
mode. I tried copying also clamd into init directory.
Neither do I. Why not use an official version from clamav.net?
Hello Trog,
running clamd through gdb results in this backtrace:
(gdb) run
Starting program: /usr/local/sbin/clamd
[New Thread 1024 (LWP 23563)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 23563)]
0x4004e33f in inflate_codes () from
On 15 Dec 2004, at 4:00, Davis Lee [EMAIL PROTECTED] wrote:
On MacOS X Server there are a couple of places to look first, if fink
is installed you will have a /sw directory and clamav might be
installed under there. If it is, then the upgrade process is quite
simple:
/sw/bin/fink selfupdate
Bogusaw Brandys wrote:
HR wrote:
I've been running some tests lately, and I can not make clam block files
that exceed ArchiveMaxRecursion. I guess the same goes for the other
limits too, although I haven't tested them. clamd.conf attached inline
below. According to the log, the settings are
On Tue, 2004-12-14 at 11:08, Chikhi Hakim wrote:
WARNING: Your ClamAV installation is OUTDATED - please update
immediately !
Your ClamAV installation is outdated, please update.
Or remove the multiple old installations you have.
-trog
signature.asc
Description: This is a digitally signed
After upgrading from clamav-0.75.1 to clamav-0.80 (slackware, gcc-2.95.3)
all I get when starting clamd is: Segmentation fault.
While upgrading all looked ok, there were no errors. The log shows:
Tue Dec 14 16:06:47 2004 - +++ Started at Tue Dec 14 16:06:47 2004
Tue Dec 14 16:06:47 2004 - clamd
Just download the new source, compile it, and install it (make install). As
long as you install the newer version in the same place, all the binaries and
libaries will overwrite all the old, existing stuff...
James
Quoting Darryl W. DeLao Jr. [EMAIL PROTECTED]:
I currently have Clam .72 and I
Jason Haar wrote:
Tomasz Kojm wrote:
I use ClamAV in association with qmailscanner and SpamAssassin to
filter email. Several times in the past three days this mail server
has become unresponsive. The only things that I can think of that
has changed in that time are the virus definitions
James wrote:
Just download the new source, compile it, and install it (make install). As
long as you install the newer version in the same place, all the binaries and
libaries will overwrite all the old, existing stuff...
James
For a number of reasons you should not depend upon the installation
That did the trick!
THANKS Thomasz!!!
Did you got that out of the backtrace??
:-) AK :-)
On Tue, 14 Dec 2004 22:31:52 +0100 (CET)
[EMAIL PROTECTED] wrote:
(gdb) run
Starting program: /usr/local/sbin/clamd
[New Thread 1024 (LWP 23563)]
Program received signal SIGSEGV, Segmentation
On Tue, 14 Dec 2004 22:56:36 +0100 (CET)
AKSurF [EMAIL PROTECTED] wrote:
That did the trick!
THANKS Thomasz!!!
You're welcome.
Did you got that out of the backtrace??
Yes
--
oo. Tomasz Kojm [EMAIL PROTECTED]
(\/)\. http://www.ClamAV.net/gpg/tkojm.gpg
On Tue, 14 Dec 2004 22:31:52 +0100 (CET)
[EMAIL PROTECTED] wrote:
(gdb) run
Starting program: /usr/local/sbin/clamd
[New Thread 1024 (LWP 23563)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (LWP 23563)]
0x4004e33f in inflate_codes () from
13 matches
Mail list logo
