Re: [Clamav-users] Upgrade

2004-12-14 Thread Jonathan Trott
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 /

Re: [Clamav-users] Segmentation fault after upgrade to 0.80

2004-12-14 Thread Tomasz Kojm
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 /usr/loc

Re: [Clamav-users] Segmentation fault after upgrade to 0.80

2004-12-14 Thread Tomasz Kojm
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/tko

Re: [Clamav-users] Segmentation fault after upgrade to 0.80

2004-12-14 Thread AKSurF
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, Segm

Re: [Clamav-users] Segmentation fault after upgrade to 0.80

2004-12-14 Thread aksurf
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 /usr/local/lib/libclama

Re: [Clamav-users] Upgrade

2004-12-14 Thread Dennis Peterson
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 p

RE: [Clamav-users] Re: Starting clamd

2004-12-14 Thread Nigel Horne
> 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

Re: [Clamav-users] Upgrade

2004-12-14 Thread Davis Lee
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 <[

RE: [Clamav-users] Upgrade

2004-12-14 Thread Darryl W. DeLao Jr.
Excellent...thanks! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Sent: Tuesday, December 14, 2004 10:02 AM To: ClamAV users ML Subject: Re: [Clamav-users] Upgrade Just download the new source, compile it, and install it (make install). As long

Re: [Clamav-users] Segmentation fault after upgrade to 0.80

2004-12-14 Thread Trog
On Tue, 2004-12-14 at 15:33, [EMAIL PROTECTED] wrote: > 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 -> +++ Starte

RE: [Clamav-users] Many clamscan processes

2004-12-14 Thread Tim Howell
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

Re: [Clamav-users] Upgrade

2004-12-14 Thread James
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 a

[Clamav-users] Segmentation fault after upgrade to 0.80

2004-12-14 Thread aksurf
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

Re: [Clamav-users] freshclam

2004-12-14 Thread Trog
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 signe

Re: [Clamav-users] ArchiveBlockMax does not work?

2004-12-14 Thread HR
Bogusław 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 acknow