Noel Jones wrote the following on 6/1/2007 10:22 PM -0800:
At 11:39 PM 6/1/2007, Dennis Peterson wrote:
Noel Jones wrote:
I'm running Solaris 10 x86 here and cannot duplicate your error. I moved
the daily.wdb file to /tmp and clamd died. I restarted it with svcadm
and it started and
how can i fix this? does anyone know when will be released the rpm files of
version 0.90.3?
Thanks
freshclam --debug
ClamAV update process started at Sat Jun 2 03:24:50 2007
LibClamAV debug: Can't create Lock file for Database Directory: /usr/
Noel Jones pisze:
At 10:20 PM 6/1/2007, Christopher X. Candreva wrote:
On Fri, 1 Jun 2007, Noel Jones wrote:
fatfinger error on the name, I am referring to daily.wdb as the
pasted session shows.
Ah, sorry. Bleary-eyed error not catching it in the sesion. :-)
Are you
On Saturday 02 June 2007, Noel Jones wrote:
new main.cvd and daily.cvd. Deleting daily.cvd stopped clamscan from
dumping core for me.
It helped me too. But I use 0.90.2 and 0.90.3
--
Regards,
Sergey
___
Help us build a comprehensive ClamAV guide:
On Sat, 02 Jun 2007 00:22:48 -0500
Noel Jones [EMAIL PROTECTED] wrote:
I recompiled clamav without --enable-experimental and still have the
error. It's unclear if this flag does anything interesting right now
since the anti-phishing code is enabled by default in this version.
The
On Sat, 2 Jun 2007 16:07:26 +0500
Sergey [EMAIL PROTECTED] wrote:
and... Broken update is not good, but core dumping of clamd is very bad.
It would be good to make clamd steadier with broken updates...
First of all, the update itself was OK. Secondly, it's not possible to predict
software
On Saturday 02 June 2007, Tomasz Kojm wrote:
and... Broken update is not good, but core dumping of clamd is very bad.
It would be good to make clamd steadier with broken updates...
First of all, the update itself was OK.
The problem appeared at Jun 2 04:53:33 GMT+5 in first time with
Hello Sergey,
and... Broken update is not good, but core dumping of clamd is very bad.
It would be good to make clamd steadier with broken updates...
First of all, the update itself was OK.
The problem appeared at Jun 2 04:53:33 GMT+5 in first time with 0.90.3
the offending
At 06:29 AM 6/2/2007, Tomasz Kojm wrote:
On Sat, 2 Jun 2007 16:07:26 +0500
Sergey [EMAIL PROTECTED] wrote:
and... Broken update is not good, but core dumping of clamd is very bad.
It would be good to make clamd steadier with broken updates...
First of all, the update itself was OK. Secondly,
Noel Jones wrote:
At 11:39 PM 6/1/2007, Dennis Peterson wrote:
Noel Jones wrote:
I'm running Solaris 10 x86 here and cannot duplicate your error. I moved
the daily.wdb file to /tmp and clamd died. I restarted it with svcadm
and it started and ran file. I then rsync'd daily.wdb from /tmp back
hello
The operation of clamd is remarkably slow
CPU utilization exceeds every 20% up
until 0.90.2 version before did not have the problem of looking like this
symptom
I used Dag RPM, clamd-0.90.3-1.el4.rf.i386.rpm
For process clamd (PID 9870)
Open files
File Descriptor Type
11 matches
Mail list logo
