Programming

If the number of loops, hence the number of children, could be infinite, you really should call wait() for all its children. But you don't need to block in order to do so, just create a thread for it in the background.

Since this process is persistent, you could also create threads for this, which may be more efficient. Forking processes like this allows them to continue when the parent quits, while threads would not. Threads are also subject to race conditions(seperate contexts all in the same process sharing most of the same memory).

Hello,
My mistake of using continue and not taking care of those children properly has taken supervisord down as supervisord could not access the socket, which was already used by a program (probably one of those zombies). I killed all the instanced of the app and supervisord restarted properly.
I must take care of that issue!
Let me spend some time on understanding how threads would work here.

---------- Post updated 06-09-10 at 04:09 PM ---------- Previous update was 06-08-10 at 09:31 PM ----------

Hi,
I was able to give another looks at the supervisor's doc (the site was down for a few hours) and it appears that
This explains why I had the problems above. Now, I guess my best strategy is to use threads.