* Jesse Guardiani <[EMAIL PROTECTED]> [20030909 22:43]: wrote:
> > Tomasz,
> >
> > Are you recommending that we run the CVS version in production? That is
> > the only sure way I see of stress-testing it ;)))
>
> You could use your imagination and toss any vi
Michael St. Laurent wrote:
Is there a fix for the defunct clamd processes that happen when using the
clamav-milter? Has it been fixed in CVS yet?
I submitted a couple of fixes over the weekend, but mainly plugging
memory leaks.
These fixes are not (all) checked into CVS yet.
I think posting core
* Jesse Guardiani <[EMAIL PROTECTED]> [20030909 22:43]: wrote:
> Odhiambo Washington wrote:
>
> > * Tomasz Kojm <[EMAIL PROTECTED]> [20030909 19:07]: wrote:
> >> >
> >> > Erm... Thanks Tomasz, but as far as we could see before shutting up the
&g
Dear sir,
i lost my 'favourite', and i couldn't get the rpm file for my Redhat9?
anyone knows where can i get the rpm?
secondly, has any one experience with Netmax Linux appliance? anyone tested
clam with Netmax?
please advice,
LIM
---
This s
ClamAntiVirus
Update (09/09/2003)
I've updated the devel port to 20030909. Many thanks for everyone who sent feedback. I got lots of input about milter and ripmime, but in the end went with a milter flavor. If I get the time to screw around with ripmime, I might make that available
Doesn't gnu-pth2 work under NetBSD for this purpose?
Regards,
Flinn
On Tuesday, September 9, 2003, at 02:08 PM, Oliver Egginger wrote:
Hello,
I need posix thread support under NetBSD, cause the clamd (an open
source virus scanner) needs pthreads. I tempted to use the mit-pthread
pachage from pk
Is there a fix for the defunct clamd processes that happen when using the
clamav-milter? Has it been fixed in CVS yet?
--
"The United States is putting together a Constitution now for Iraq. Why
don't we just give them ours? It's served us well for 200 years, and we
don't appear to be using it an
Hi,
Normally they are available here:
http://activeintra.net/projects/clamav/ (it's Flinn's website), because
Flinn is the maintainer of the port. However, it seems that Flinn is
busy with other things, so I took over the maintainership for now.
Feel free to mirror it yourself for now. I'll ke
Hello,
I need posix thread support under NetBSD, cause the clamd (an open
source virus scanner) needs pthreads. I tempted to use the mit-pthread
pachage from pkg-src but it's unfit for this task, cause required
pthread functions are'nt implemented yet.
;-(
At the moment I'am working with NetBSD 1
Odhiambo Washington wrote:
> * Tomasz Kojm <[EMAIL PROTECTED]> [20030909 19:07]: wrote:
>> >
>> > Erm... Thanks Tomasz, but as far as we could see before shutting up the
>> > scanner, there was no core. I just searched and found none, too.
>>
>
Hello all,
I thought I remembered something about this, but I can't find it
anywhere in my archives of this list. Does clamd not play nice with
logrotate? I just set it up and ran it by hand and clamd was still
running and doing its thing, but it stopped logging. I had to stop
clamd (and it hel
This port looks like it has solved my problem with clamd bombing on me.
I would like to summarize how I did the setup and install for others
running Postfix, Amavisd-new, and Spamassassin on OpenBSD 3.3 in chroot
jail that have reported similar problem. Is there an ftp or http site
were the previo
* Tomasz Kojm <[EMAIL PROTECTED]> [20030909 19:07]: wrote:
> >
> > Erm... Thanks Tomasz, but as far as we could see before shutting up the
> > scanner, there was no core. I just searched and found none, too.
>
> Please recompile clamav with --enable-debug
Tomasz,
>
> Erm... Thanks Tomasz, but as far as we could see before shutting up the
> scanner, there was no core. I just searched and found none, too.
Please recompile clamav with --enable-debug
> Well, what we could observe was the inability of exim and clamd to talk (or
Best regards,
Tomasz Kojm
--
On Tue, Sep 09, 2003 at 03:34:04PM +0200, Tomasz Kojm wrote:
> > Is this a well known (new) issue for the *frontend* or is the scanning
> > *engine* itself broken? If it is a frontend issue, we might be encouraged to
> > hack a new (unthreaded) stable frontend for the engine.
>
> Could you manag
> Is this a well known (new) issue for the *frontend* or is the scanning
> *engine* itself broken? If it is a frontend issue, we might be encouraged to
> hack a new (unthreaded) stable frontend for the engine.
Could you manage to catch the core file ? Without it we can't help you
and answer on th
> On Fri, Sep 05, 2003 at 10:11:41AM +0200, Marian Eichholz wrote:
>
> > > I had to downgrade to the clamav-20030829.tar.gz which apparently is
> > > stable on my FreeBSD 4.8. I also use exim-4.22/exiscan.
>
> Hmm... Our upgrade to 20030829 still shows the well known issue with a dying
> clamd an
Hi!
A test deploy of development release 09/08 was unfortunately no success at all.
In fact the Exim/Exiscan (4.22) cannot connect to the clamd-socket any
longer (the connect() blocks).
So we had to shut down virus prevention, since the old releases are proven
to be instable, too, and we cannot
On Fri, Sep 05, 2003 at 10:11:41AM +0200, Marian Eichholz wrote:
> > I had to downgrade to the clamav-20030829.tar.gz which apparently is
> > stable on my FreeBSD 4.8. I also use exim-4.22/exiscan.
Hmm... Our upgrade to 20030829 still shows the well known issue with a dying
clamd and exim process
This might be old , but I do notice a vulnerability
in that if clamav-milter has to much checkingto do,
the progam spawns another children and keeps growing.
Any way to control this behaviour?
---
This sf.net email is sponsored by:ThinkGeek
Wel
20 matches
Mail list logo
