loop in run-events

[Herb Lewis]

This is with samba 3.2.4

I ran into a case where run_events seemed to be in an infinite loop.
Here were the log messages that kept repeating. It seems the event
never got cleared. ps showed the process that could not be contacted
was in zombie state and do_sigchld was 1 but since run_event never
finished the code to reap the child could not get called.

The question is where should this event have been removed?

[2009/02/09 21:55:01,  0, pid=8860] PANIC: assert failed at 
freebsd_46_i386/release/build/samba/source/winbindd/winbin
dd.c(718): state->response.result == WINBINDD_PENDING
[2009/02/09 21:55:01,  0, pid=8860] PANIC: assert failed at 
freebsd_46_i386/release/build/samba/source/winbindd/winbin
dd.c(623): event->flags == 0
[2009/02/09 21:55:01, 10, pid=8860] Running event 
"async_request_timeout" 8638530
[2009/02/09 21:55:01,  0, pid=8860] async_request_timeout_handler: child 
pid 15040 is not responding. Closing connecti
on to it.
[2009/02/09 21:55:01,  5, pid=8860] Could not receive async reply from 
child pid 15040
[2009/02/09 21:55:01,  5, pid=8860] Could not trigger gid2sid
[2009/02/09 21:55:01,  0, pid=8860] PANIC: assert failed at 
freebsd_46_i386/release/build/samba/source/winbindd/winbin
dd.c(718): state->response.result == WINBINDD_PENDING
[2009/02/09 21:55:01,  0, pid=8860] PANIC: assert failed at 
freebsd_46_i386/release/build/samba/source/winbindd/winbin
dd.c(623): event->flags == 0
[2009/02/09 21:55:01, 10, pid=8860] Running event 
"async_request_timeout" 8638530
[2009/02/09 21:55:01,  0, pid=8860] async_request_timeout_handler: child 
pid 15040 is not responding. Closing connecti
on to it.