> Matus UHLAR - fantomas wrote: > > 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...
On 23.12.08 07:23, Jim Preston wrote: > I agree that clamd shouldn't crash but......it is certainly not always a > hardware issue. I used to have problem with the clamav-milter crashing > every day. I added a cron job to restart it. Do not remember which > version it was but was in the 0.9.x family. One of the upgrades fixed > the problem. Since this happened on only one of my systems, I chalked it > up to system specific. clamav-milter was reported to be in fact an old version of clamav, with milter interface. The new version of milter shouldn't support direct scanning and will be forced to use clamd: http://lurker.clamav.net/message/20081205.152347.a7d7c9ee.en.html I recommend you running it in remote mode, using real clamav to scan files. It's also more memory effective (I checked that!), especially in case where the OP uses clamdscan from procmail for files fetched from remote mailbox. -- 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. A day without sunshine is like, night. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
