Thank you very much for your answers. Felipe's suggestion to use waitForProcess after terminateProcess did the trick. No more zombies around :)
Best regards, Dan Rosén On Wed, Dec 7, 2011 at 4:39 PM, Donn Cave <d...@avvanta.com> wrote: > Quoth Felipe Almeida Lessa <felipe.le...@gmail.com>, > > On Wed, Dec 7, 2011 at 1:19 PM, Brandon Allbery <allber...@gmail.com> > wrote: > >> They *do* terminate; a zombie is a dead process waiting for its parent > to > >> reap it with waitForProcess. There's also some POSIX stuff you can do > to > >> have them auto-reaped, but doing that correctly and portably is somewhat > >> painful. > > > > But zombie processes do consume a row in the process table, right? If > > so, then it's bad to have them around. > > Correct. As noted above, clean up with waitForProcess to release this > resource. If it's more convenient, that could be done up front, by > forking twice and waiting for the intermediate process. One possibly > convenient way to do that might be something like runCommand "eprover &". > > Donn > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
