On 7/23/07, Lystopad Oleksandr <[EMAIL PROTECTED]> wrote: > (gdb) info thread > 3 Thread 0x8057000 (LWP 100087) 0x282c377f in accept () from /lib/libc.so.6 > 2 Thread 0x9fb6100 (LWP 100078) 0x2830f83b in __vfprintf () from > /lib/libc.so.6 > * 1 Thread 0x9bc3400 (LWP 100099) 0x2830f83b in __vfprintf () from > /lib/libc.so.6 > [..] > (gdb) bt > #0 0x2830f83b in __vfprintf () from /lib/libc.so.6 > #1 0x2829dcf0 in vsnprintf () from /lib/libc.so.6 > #2 0x2809480e in cli_dbgmsg () from /usr/local/lib/libclamav.so.2 > #3 0x280936f6 in cli_validatesig () from /usr/local/lib/libclamav.so.2
So it was wasting time writing debug messages. (as you can see for yourself from the backtraces) > > And first server, where I make ``Debug no'' in config about 3 hours > no problem at all! Business time with high mail activity and no problems with > clamd! I'll continue follow the clamd. > Ok. But why was debugging turned on in the first place? Some sample config you found somewhere? --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
