Hi,
I am not sure why. But my dual xeon with libthr on clamav-90.1 still gives
very high cpu usage.
It's the same case here. What happens if you limit kern.smp.maxcpus
to 1 ? Does it still use the same amount cpu time ? What happens if
you link clamd against libc_r ?
--
Martin
Hi,
I just fixed those issues with the port.
Thanks for reporting !
Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED]
--
ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 61 826 93 00 Fax: +41 61 826 93
Hi,
Don't use it, it's broken.
-trog
Nope, it looks like a race in cli_scanmail() which deadlocks somewhere
with libpthread.so. This workaround fixes the problem for me. I'm still
investigating where the real cause for this problem is.
--- libclamav/scanners.cTue Feb 13 02:06:28
Hi all,
After adding some debug stuff to clamd running with freebsd
libpthread.so I found that:
looking at the output value of 'ps -auxH | grep clamd | grep -v grep | wc -l'
is always staying at 6 threads, but the number of threadpool-thr_alive is
going higher and higher. So
Hi,
Make sure clamd is checking the return value of pthread_create()
for errors. You can also set LIBPTHREAD_PROCESS_SCOPE=yes or
LIBPTHREAD_SYSTEM_SCOPE=yes in your environment to force process
scope or system scope threads (libpthread only) for clamd.
Yes, it does check the return value.
