On 05/21/2010 08:40 AM, Dennis Peterson wrote: > On 5/20/10 10:27 PM, Dennis Peterson wrote: >> While testing my build of 0.96.1 today I was alerted by a screen message >> on starting clamd that I had two bytecode files - compressed and >> uncompressed. I removed the uncompressed file and restarted clamd. Later >> I checked the log to see if there was more information I could add to >> logwatch and there was no reference at all of this event. I'm using >> syslog. That is exactly the kind of information I'd expect to find in >> the log and I guess I wonder why it wasn't there. So, why isn't it there? > > > And there's more to the story. In tracking down what happened above I > ran freshclam from the command line and got this: > > $ freshclam > ClamAV update process started at Thu May 20 22:39:04 2010 > main.cld is up to date (version: 52, sigs: 704727, f-level: 44, builder: > sven) > daily.cld is up to date (version: 11061, sigs: 81529, f-level: 51, > builder: acab) > Downloading bytecode.cvd [100%] > LibClamAV Error: cli_calloc(): Can't allocate memory (0 bytes). > calloc_problem: Error 0 > LibClamAV Error: Out of memory allocating operands
I don't get this error, what OS/arch is this? > ERROR: Failed to load new database: Malformed database This message was in freshclam's log though, right? Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml