On 2011-08-11 22:02, ulises gonzalez wrote:
> On Thursday 11 August 2011 02:29:17 pm Török Edwin wrote:
>> How? Is it a SIGSEGV/SIGBUS/something else?
>
>
> Excuse me, how I can do this...??
Following the instructions on the clamav website on how to attach gdb to clamd,
then wait for the selfch
I've been having the same issue with my Linux FC 8 X86_64. ClamAV
0.96.5/13427/Wed Aug 10 16:31:52 2011 (I know its old, I need to update)
I use the old restarting the daemon every night method. It seems to work for me.
> From: uli...@mfp.gov.cu
> To: clamav-users@lists.clamav.net
> Date: Thu
On Thursday 11 August 2011 02:29:17 pm Török Edwin wrote:
> How? Is it a SIGSEGV/SIGBUS/something else?
Excuse me, how I can do this...??
> Grep your dmesg for messages about clamd (segfaults are usually logged
> there). Also see if clamd created a core file.
There is nothing in dmesg
serverg
On 2011-08-11 21:12, ulises gonzalez wrote:
> Hello everybody:
>
> I've been using Clamav since 2005 on Ubuntu and Debian sistems, since one
> year I've been compiling it with the clamuko module (versions 0.96.2 to
> 0.97.2 excluding 0.97.1) joined to this I've been compiling to dazukofs.
Hello everybody:
I've been using Clamav since 2005 on Ubuntu and Debian sistems, since one
year I've been compiling it with the clamuko module (versions 0.96.2 to
0.97.2 excluding 0.97.1) joined to this I've been compiling to dazukofs.
With all theese versions of clamav clamav dies sudenly
