> > check clamd logs On 23.12.08 08:58, Robert S wrote: > There's nothing in the logs at the time the error occurs. I have however > discovered some of these in my syslog (see last line): [...] > Dec 15 01:00:21 mypc freshclam[1230]: Clamd was NOT notified: Can't connect > to clamd through /var/run/clamav/clamd.sock [...] > Dec 2 12:34:54 mypc clamd[1221]: segfault at 8eec7e8 ip 7f9fc0a5da11 sp > 7fffc8f19990 error 4 in libclamav.so.5.0.4[7f9fc0a43000+ab000] > > Maybe I need a cron job to restart clamd when it dies (like the old days). > It looks as if clamav-milter runs fine. I'm using clamav-0.94.2 (gentoo). > > Any solutions? What is "error 4"?
I have no idea, but something look broken on your system. If upgrading it won't help, you should check HW, memory at first. clamd shouldn't crash... -- Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. "They say when you play that M$ CD backward you can hear satanic messages." "That's nothing. If you play it forward it will install Windows." _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
