Hi, 2012/7/17 Ben Noordhuis <[email protected]>
> > `type` is a no-op now. `fd` works with some restrictions: use `new > Socket(fd)` instead - if fd is a socket, it must be of type > SOCK_STREAM. > I've tried this with no luck. I still see that a new socket is created. The code I'm using is here: https://gist.github.com/3129376, and the missing C++ binding are copied from the ones in node-unix-dgram module. Running it with strace confirms the creation of the new socket: socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 7 bind(7, {sa_family=AF_FILE, path="/tmp/sock_terminal_node"}, 110) = 0 socket(PF_FILE, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 8 connect(8, {sa_family=AF_FILE, path="/tmp/echo_socket"}, 110) = 0 getsockopt(8, SOL_SOCKET, SO_ERROR, [0], [4]) = 0 Any ideas? Thanks, Santi -- 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
