Hello, I have been running clamd (0.65) on our mail server (Red Hat Linux 8 with kernel 2.4.20) for a few months without any problems at all.
Recently I decided to include Dazuko support in the kernel and enable Clamuko in clamd. This is up and running and works just fine apart from one problem. Every time the virus database is updated (by freshclam) clamd will abort with a segmentation fault. What I see in clamd.log is typically this: Thu Dec 11 10:07:37 2003 -> SelfCheck: Database modification detected. Forcing reload. Thu Dec 11 10:07:38 2003 -> Reading databases from /usr/local/share/clamav Thu Dec 11 10:07:38 2003 -> Database correctly reloaded (21438 viruses) Thu Dec 11 10:10:23 2003 -> Segmentation fault :-( Bye.. The segmentation fault always appear a few minutes after the database update. This has happened consistently now at least 4 or 5 times. If I disable Clamuko, clamd continues to live happily even after a database update. If there are no database updates, clamd will run fine even with Clamuko enabled. Any suggestions as to what might be the problem? Anders ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
