Milter-greylist

On Wed, Feb 12, 2014 at 08:07:54PM +0100, manu@... wrote:
> Johann Klasek <johann@...> wrote:
> 
> > Is there any hint what these threads are doing?
> 
> All sleeping. I suspect libmilter fails to track threads and leaves some
> behind.

I think libmilter does not actually tracking his threads. They are
created/cloned to process a SMTP-session and self-terminate later ...

Have you a sample for a backtrace of your threads? Are they all the
same (beside the organizational ones)?

With Linux Fedora 16 most of the workers looks like this:

Thread 2 (Thread 0x7f6f2cc13700 (LWP 21649)):
#0  0x00000036df0e8283 in select () from /lib64/libc.so.6
#1  0x000000000041fbd5 in mi_rd_cmd ()
#2  0x000000000041f3ec in mi_engine ()
#3  0x000000000041c478 in mi_handle_session ()
#4  0x000000000041b129 in mi_thread_handle_wrapper ()
#5  0x00000038a8807d90 in start_thread () from /lib64/libpthread.so.0
#6  0x00000036df0eeddd in clone () from /lib64/libc.so.6

beside the dumper, sync_master, sync_sender and Signaling thread.