-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSX Bad File Descriptor Issue? #2
Comments
Hey, I am not sure if you are still interested in this but today I was busy probably with the same thing. I bet you mean this error "Getting (libev) kevent: Bad file descriptor on OSX" happening only on your OSX right? There you can find the function ev_default_fork(). From the description I understand that the event loop need to reinitialized after fork() of new process, so I've added the call right after the new process is created. Did help with the error, but I got different one though. Not sure what it is but perhaps looks like something else got corrupted. This is the output I have: node.js:116 I am trying to setup new http.Server after the fork btw. |
This is my current code btw https://github.com/petrjanda/daemon.js/blob/feature%2Fdaemon-cpp/src/daemon.cc |
@petjanda Interesting! I'll have to play around with this sometime soon. |
Then please ping me once you will make some progress in that, I will do the same. |
Is there any movement on this bug? I am running daemon.node 0.5.1, node 0.8.14, Mac OSX 10.8.2 and this still seems to be happening. Is any plan to make this work on Max OSX? Thanks and here is the test code:
|
I can confirm that this is an issue with node v0.3.0:
http://slashed.posterous.com/writing-daemons-in-javascript-with-nodejs-0#pcomment_commentunit_5698960
Any thoughts here? We run on both Ubuntu (production) and OSX (development) environments, so we need a cross-platform solution.
The text was updated successfully, but these errors were encountered: