On Thursday 08 of April 2004 02:11, Tomasz Kojm wrote:
> On Wed, 7 Apr 2004 01:57:23 +0200
>
> For a "very simple mail scanner" the (b) solution seems to be the best
> IMHO.
Well, anyway it would be great, if someday ClamAV distribution includes
something like "libclamdclient". Looking at clamdsc
On Wed, 7 Apr 2004 01:57:23 +0200
Przemyslaw Wegrzyn <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I'm about to include clamavis support in our very simple mail scanner.
> My first idea was to use libclamav for that, however my filter will be
>
> integrated with our mail server in the way that it will be
Hi!
I'm about to include clamavis support in our very simple mail scanner. My
first idea was to use libclamav for that, however my filter will be
integrated with our mail server in the way that it will be spawned for each
mail.
For obvious performance reason I'd like to use clamd, but I've fo
> If you have can put an accurate time on when clamd stopped
> responding, would it correspond to their being a virus DB update?
I don't think so.
> I assume that you do automatic updates and this is signalled
> to clamd (probably via freshclam --daemon-notify).
That's true, I am doing automat
Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
> > So, how is clamd behaving with the patch and ThreadTimout=0?
> >
> > Is it any better?
>
> It is actually better, but unfortunately, there still seems to be a
> problem
> somewhere.
If you have can put an accurate time on when clamd stopped r
> So, how is clamd behaving with the patch and ThreadTimout=0?
>
> Is it any better?
It is actually better, but unfortunately, there still seems to be a problem
somewhere. Here is what gdb shows me:
GNU gdb 5.3.92
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the
> So, how is clamd behaving with the patch and ThreadTimout=0?
>
> Is it any better?
Yes, indeed. It didn't crash since one day now. I will continue to observe.
Regards,
Phil.
---
The SF.Net email is sponsored by EclipseCon 2004
Premiere Con
Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
>
> Thank you for the patch, I will apply it and re-compile clamd.
>
So, how is clamd behaving with the patch and ThreadTimout=0?
Is it any better?
Cheers,
-trog
---
The SF.Net email is sponso
On Thu, 15 Jan 2004 16:45:20 + (GMT)
Trog <[EMAIL PROTECTED]> wrote:
> Quoting Tomasz Kojm <[EMAIL PROTECTED]>:
>
> > >
> > > Your patch is incorrect. It will always be true for threads that
> > > are currently in use and they will instantly be killed.
> >
> > I disagree. The patch does the
Quoting Tomasz Kojm <[EMAIL PROTECTED]>:
> >
> > Your patch is incorrect. It will always be true for threads that are
> > currently in use and they will instantly be killed.
>
> I disagree. The patch does the same thing that yours.
>
You patched a different line of code, so the argument is moo
On Thu, 15 Jan 2004 14:37:56 + (GMT)
Trog <[EMAIL PROTECTED]> wrote:
> Quoting Tomasz Kojm <[EMAIL PROTECTED]>:
>
>
> > Oh, you're right - there was no chance to disable the timeout
> > (however clamav.conf states that 0 disables the limit). It's even
> > better to use:
> >
> > if(timeout &
Quoting Tomasz Kojm <[EMAIL PROTECTED]>:
> Oh, you're right - there was no chance to disable the timeout (however
> clamav.conf states that 0 disables the limit). It's even better to use:
>
> if(timeout && ths[i].active)
>
> instead of
>
> if(timeout && (time(NULL) - ths[i].start > timeout))
>
On Thu, 15 Jan 2004 13:27:16 + (GMT)
Trog <[EMAIL PROTECTED]> wrote:
> Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
>
>
> > > Timed out after 3 seconds! Thats not right.
> > >
> > > A quick look at the code, and it seems that the thread
> > > timeout code isn't correct.
> > >
> > > It
> Do:
>
> cd /clamav-0.65/clamd
> patch -p0 < /path/to/clamd.timeout.patch
>
> and in clamav.conf set this:
>
> ThreadTimeout 0
Thank you for the patch, I will apply it and re-compile clamd.
I also saw in the log file, that whenever clamd crashes, the last line
logged is something like this:
Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
> > Timed out after 3 seconds! Thats not right.
> >
> > A quick look at the code, and it seems that the thread
> > timeout code isn't correct.
> >
> > It is also possible that there is a mutex locking bug in clamd.
>
> Could this be the cause of
Quoting Tomasz Kojm <[EMAIL PROTECTED]>:
> On Thu, 15 Jan 2004 09:49:22 + (GMT)
> Trog <[EMAIL PROTECTED]> wrote:
>
> > [EMAIL PROTECTED] gale]$ clamdscan .
> > /home/gale/./.mozilla/default/5bc4ycs6.slt/Cache/_CACHE_002_:
> > Eicar-Test-Signature FOUND
> > Session(0): Time out ERROR
> >
> >
Quoting Tomasz Kojm <[EMAIL PROTECTED]>:
> On Thu, 15 Jan 2004 09:49:22 + (GMT)
> Trog <[EMAIL PROTECTED]> wrote:
>
> > [EMAIL PROTECTED] gale]$ clamdscan .
> > /home/gale/./.mozilla/default/5bc4ycs6.slt/Cache/_CACHE_002_:
> > Eicar-Test-Signature FOUND
> > Session(0): Time out ERROR
> >
> >
On Thu, 15 Jan 2004 09:49:22 + (GMT)
Trog <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] gale]$ clamdscan .
> /home/gale/./.mozilla/default/5bc4ycs6.slt/Cache/_CACHE_002_:
> Eicar-Test-Signature FOUND
> Session(0): Time out ERROR
>
> Timed out after 3 seconds! Thats not right.
There was a ra
> clamd will be linked against libpthread, the command 'ldd
> /usr/local/sbin/clamd' should so this.
The command shows the following output:
libclamav.so.1 => /usr/local/lib/libclamav.so.1 (0x4001a000)
libz.so.1 => /lib/libz.so.1 (0x4003c000)
libbz2.so.1 => /usr/lib/libbz
Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
> OK, clamd already crashed once again, and now I was trying to follow
> your
> guide...
>
> > (I'm going to assume you're clamd is multithreaded. If not
> > just do steps 1-3 followed by the command 'bt').
>
> I think so, how can I tell?
clamd w
OK, clamd already crashed once again, and now I was trying to follow your
guide...
> (I'm going to assume you're clamd is multithreaded. If not
> just do steps 1-3 followed by the command 'bt').
I think so, how can I tell?
> This may, or may not, provide some useful information.
>
> 1. Use 'ps
> The following is composed of wild conjecture and guesses...Just looking
> at the symptoms I've seen discussed here, it sounds like something is
> happening to cause a clamd child to stop responding and not exit(). And
> somehow this child not exit()ing is preventing clamd from spawing more
> ch
On Wed, 2004-01-14 at 10:57, Trog wrote:
> But, perhaps it's just me, but I don't quite understand why
> people are writing such scripts instead of spending their effort
> actually trying to fix the problem.
I've had it happen ~3 times in the last year. Each time it crashes,
there are thousands o
Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
>
> However, if you tell me exactly (step by step) what I have to do to give
> you
> more information, I will try my best. I am very happy with ClamAV so far
> and
> I want to support it.
>
(I'm going to assume you're clamd is multithreaded. If n
> What version are you running?
ClamAV 0.65
> A number of people have reported this issue and it has
> resulted in scripts being written that check the status of
> clamd periodically and restart it.
I heard about that, but I was asking about doing this remotely, since spamd
itself is actually
Quoting Philipp Grosswiler <[EMAIL PROTECTED]>:
> I would like to know how I can remotely restart the clamd server... or
> actually kill all the processes.
>
> It happens that clamd sometimes is not working correctly anymore, but I
> can
> still remotely access it and send commands. I am using cl
I would like to know how I can remotely restart the clamd server... or
actually kill all the processes.
It happens that clamd sometimes is not working correctly anymore, but I can
still remotely access it and send commands. I am using clamd (running on
Linux) to scan the mail server (running on Wi
27 matches
Mail list logo
