I ran into this issue because of a refactor. We started using libuv's threadpooling functionality in an application that already used forks. It's not that I want to fork, but the code already did and I was hoping to offer some protection that a forked program wouldn't end up aborting on shutdown.
This pull request shouldn't be merged as it doesn't work, I was just working through this with Fedor and he asked for a pull request instead of a diff. It's probably something we can drop just on the merit of the possible performance implications and the general problems of forks and threads. On Monday, July 7, 2014 3:18:03 AM UTC-6, Andrius Bentkus wrote: > > Why are you trying to fork if the kqueue is not supporting forks? > -- You received this message because you are subscribed to the Google Groups "libuv" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/libuv. For more options, visit https://groups.google.com/d/optout.
