Last night I experienced the same lock-up I reported previously. I was unable to capture any debug information (I was sleeping at the time, and my monitoring detected the problem and auto-restarted clamd). From looking at my logs I can say definitively that the problem occured while re-loading the virus database, though.
To re-cap, I'm running clamd devel-20031106 on FreeBSD 4.8. The last entries in my log were: Nov 8 07:00:55 barium clamd[43617]: SelfCheck: Database modification detected. Forcing reload. Nov 8 07:00:55 barium clamd[43617]: SelfCheck: Integrity OK Nov 8 07:00:55 barium clamd[43617]: Reading databases from /usr/local/share/clamav Nov 8 07:06:15 barium clamd[33948]: Daemon started. As before, this happened on both of my servers at approximately the same time (after a freshclam run from cron at 6am). Definitely a reproducable problem. :( Again, let me know if I can provide any more diagnostic information to help track down the problem. Tim Wilde -- Tim Wilde [EMAIL PROTECTED] Systems Administrator Dynamic DNS Network Services http://www.dyndns.org/ ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
