Re: Defunct processes Clamav

[Tom Evans <tom@23palmer.net>]

Are you using stable, testing or unstable?

There is a problem with newer libc and linuxthreads - threads do not 
properly cleanup
after exiting and leave <defunct> processes hanging around.

I submitted a comments showing the exact location of the problem, but 
the glibc
folks seem totally uninterested in supporting the old linuxthreads package.

I would submit a patch myself, but the glibc dev setup is 
incomprehensible (imho).

This issue cause me to re-install most of my systems with "stable" 
because unstable and testing had the broken libc.


...tom
Dermot Paikkos wrote:
> Hi
>
> Debian 3.1, kernel 2.4.27-2-generic alpha GNU/Linux
> clamd daemon 0.88.2 (OS: linux-gnu, ARCH: alpha, CPU: alpha) with 
> ExiScan.
>
> I have been getting hundreds of defunct clamd processes per day.
>
> clamav   26088 18934  0 13:54 ?        00:00:00 [clamd] <defunct>
> clamav   26197 18934  0 13:55 ?        00:00:01 [clamd] <defunct>
> clamav   26287 18934  0 13:56 ?        00:00:00 [clamd] <defunct>
> clamav   26536 18934  0 13:59 ?        00:00:00 [clamd] <defunct>
> clamav   26736 18934  0 14:01 ?        00:00:00 [clamd] <defunct>
> clamav   26804 18934  0 14:01 ?        00:00:00 [clamd] <defunct>
>
> I first noticed this when my system became un-responsive and I had to 
> hit the re-set button.
>
> The processes are all children spawned by clamd which is being called 
> by exim (exiscan) to virus-check mail. The processes are left in a 
> zombie state when they should exit gracefully.
>
> I have tried getting some help from the clamav list but that what we 
> tried has not been successful in stopping the problem. I did send 
> some strace output to one helpful user. 
>
> Has anyone else seen this behaviour? Can anyone offer any advice?
> TIA.
> Dp.
>
>
> Has anyone else seen this behaviour? 
>
>
>