On Jul 29, 2004, at 00:32, Trog wrote:
On Wed, 2004-07-28 at 23:16, Doug Hardie wrote:
I was using clamav-0.70-rc for a long time because it was stable and
never crashed. However, it started missing a lot of newer viruses so I
upgraded to the version above.
Clamd is giving a segment violation every 2 to 6 hours and I have to
restart it. Thousands of messages are scanned while it is still
running. I have used the following different configure commands and I
don't see any real change in the behavior:
Please attach gdb to the running clamd and do a backtrace when it crashes.
Here is the first attempt:
[Switching to process 86282, thread 2]
Program received signal SIGSEGV, Segmentation fault. 0x281299a9 in _spinlock_debug () from /usr/lib/libc_r.so.4 (gdb) Continuing.
I have no idea why it decided to continue at that point. Anyway it just quit as normal so I couldn't get anything useful. Trying again. Somehow I manage to miss the crashes.....
------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
