[Clamav-users] clamd scanner error

2003-10-06 Thread greg gede
does anybody know why do i keep getting the following error messages in my log??? : Oct 6 14:54:32 mail X-Qmail-Scanner-1.20rc3: [some.mail.ac.id10654268704561409] clam_scanner: corrupt or unknown clamd scanner error or memory/resource/perms p roblem - exit status 2 something seems to be

Re: [Clamav-users] New db container

2003-10-06 Thread Lionel Bouton
Tomasz Kojm said the following on 10/06/2003 09:32 AM: What about climb down from trees and take some more modern protocol like rsync? ;-) Rsync is not as popular as http ;) I don't see problem here because usually the updates are very small (the main database is updated ocasionally. Best

Re: [Clamav-users] clamd scanner error

2003-10-06 Thread Flinn Mueller
make sure clamav is compiled --with-user=qscand --with-group=qscand (or whatever you are using for qmail-scanner) or set the User option in clamav.conf On Monday, October 6, 2003, at 04:00 AM, greg gede wrote: does anybody know why do i keep getting the following error messages in my log??? :

Re: [Clamav-users] New db container

2003-10-06 Thread Tomasz Kojm
Could you describe the cwd file more in depth Tomasz ? I'd like to be Documentation and support in clamav (CVS) will be available tomorrow. Best regards, Tomasz Kojm -- oo. [EMAIL PROTECTED] (\/)\. http://www.konarski.edu.pl/~zolw \..._ I

Re: [Clamav-users] New db container

2003-10-06 Thread Kritof Petr
Lionel Bouton wrote: The popularity doesn't really matter on the client side, rsync is readily available for all Unices and quite easy to get for Cygwin. The problem is that on the servers' side (main site and mirrors) you'll have to set up rsync servers instead of http servers. As a mirror

Re: [Clamav-users] New db container

2003-10-06 Thread Daniel J McDonald
On Mon, 2003-10-06 at 07:42, Kritof Petr wrote: Lionel Bouton wrote: The problem is that on the servers' side (main site and mirrors) you'll have to set up rsync servers instead of http servers. As a mirror admin this won't be good news for me... rsync server setup isnt hard.

Re: [Clamav-users] Updated: clamav-devel-20030926 (OpenBSD Port)

2003-10-06 Thread Flinn Mueller
Hey, are you still having issues with this? I am running 20030926 from my port, and I haven't had a single segfault with it. Regards, Flinn On Saturday, September 27, 2003, at 12:11 PM, Wouter de Vries wrote: Not freshclamd is the problem, clamd is. When it sees the db has been modified,

Re: [Clamav-users] Updated: clamav-devel-20030926 (OpenBSD Port)

2003-10-06 Thread Tomasz Kojm
Hey, are you still having issues with this? I am running 20030926 from my port, and I haven't had a single segfault with it. Unfortunately the race condition with db reloading is still there :( Best regards, Tomasz Kojm -- oo. [EMAIL PROTECTED] (\/)\.

Re: [Clamav-users] New db container

2003-10-06 Thread Kritof Petr
Daniel J McDonald wrote: On Mon, 2003-10-06 at 07:42, Kritof Petr wrote: Lionel Bouton wrote: The problem is that on the servers' side (main site and mirrors) you'll have to set up rsync servers instead of http servers. As a mirror admin this won't be good news for me... rsync

Re: [Clamav-users] New db container

2003-10-06 Thread Daniel J McDonald
On Mon, 2003-10-06 at 09:00, Kritof Petr wrote: Daniel J McDonald wrote: But this is only the beginning. You also have to set up new firewall rules - probably on the box itself and on the front-end firewall protecting the box. And you might have to add load-balancer rules. And if you

Re: [Clamav-users] New db container

2003-10-06 Thread Miguel Bettencourt Dias (Netopia)
On Mon, 2003-10-06 at 15:00, Kritof Petr wrote: Daniel J McDonald wrote: On Mon, 2003-10-06 at 07:42, Kritof Petr wrote: Lionel Bouton wrote: The problem is that on the servers' side (main site and mirrors) you'll have to set up rsync servers instead of http servers. As a

RE: [Clamav-users] New db container

2003-10-06 Thread Shayne Lebrun
Ok, so you already have apache bound to port 80. How do you bind the rsync server to port 80 as well? As a client, you're not running an rsync server, you're running an rsync client. Muskoka.com 115 Manitoba Street Bracebridge, Ontario P1L 2B6 (705)645-6097 Muskoka.com is pleased to announce

[Clamav-users] Clamav excludes

2003-10-06 Thread Chris de Vidal
I wrote a clamscan cron script like this: source /etc/clamav.excludes clamscan $EXCLUDES --recursive --quiet / The clamav.excludes file looks like this: EXCLUDES=\ --exclude=/foo \ --exclude=/foo/bar \ --exclude=/foo/baz \ This had been working _great_ until I needed to exclude

Re: [Clamav-users] Updated: clamav-devel-20030926 (OpenBSD Port)

2003-10-06 Thread Flinn Mueller
Maybe I can sponsor that ;-) On Monday, October 6, 2003, at 09:14 AM, Tomasz Kojm wrote: Hey, are you still having issues with this? I am running 20030926 from my port, and I haven't had a single segfault with it. Unfortunately the race condition with db reloading is still there :( Best

Re: [Clamav-users] Clamav excludes

2003-10-06 Thread Chris de Vidal
I forgot to mention I also tried editing /etc/clamav.conf: ClamukoExcludePath /foo/bar/something with spaces/tmp I also tried ClamukoExcludePath /foo/bar/something with spaces/tmp and ClamukoExcludePath /foo/bar/something\ with\ spaces/tmp /dev/idal --- Chris de Vidal [EMAIL PROTECTED] wrote:

[Clamav-users] building from cvs

2003-10-06 Thread Niklas Saers Mailinglistaccount
Hi, for a few days now I've been getting the following error when compiling clamav from CVS on a FreeBSD 5-system. Any ideas as to how to resolve this issue? gcc -DPACKAGE_NAME=\\ -DPACKAGE_TARNAME=\\ -DPACKAGE_VERSION=\\ -DPACKAGE_STRING=\\ -DPACKAGE_BUGREPORT=\\ -DPACKAGE=\clamav\

Re: [Clamav-users] clamd dies forever!

2003-10-06 Thread Ed Vazquez
On Thu, 2 Oct 2003 09:55:04 +0300 Odhiambo Washington [EMAIL PROTECTED] wrote: Okay, I know this is not good at all, that I run the CVS version of clamav on a production box. It's suicide. I've run the daily snapshots for some time without disappointment when it comes to supervising the

Re: [Clamav-users] clamd scanner error

2003-10-06 Thread greg gede
thank you, your suggestion seems to work. in clamav.conf i set User option with qscand.now, no more such error in my log file. --- Flinn Mueller [EMAIL PROTECTED] wrote: make sure clamav is compiled --with-user=qscand --with-group=qscand (or whatever you are using for qmail-scanner) or set