How does the standard library cluster module pass a newly-opened file
descriptor from a parent process to a child process in a way that
allows the child process to accept(2) and not get EBADF?

I made it to src/tcp_wrap.cc and from there into libuv and then got lost.

I only care about Linux.  Does it use the CLONE_FILES flag to
clone(2)? (I don't think it does because I can't find it in the source
code but this seems to me like the only sane way to accomplish this.)

I would greatly appreciate any explanation anyone can provide.  Thanks,

Richard

-- 
Job Board: http://jobs.nodejs.org/
Posting guidelines: 
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to