From: Joel Reymont <joelr1@gmail.com>
To: Gerd Stolpmann <gerd@gerd-stolpmann.de>
Cc: OCaml List <caml-list@inria.fr>
Subject: ocamlnet: EAFNOSUPPORT on Max OSX
Date: Sat, 5 May 2007 13:40:13 +0100 [thread overview]
Message-ID: <71B2C4B5-3ECB-450F-B015-3C5EAB90855F@gmail.com> (raw)
Gerd,
Netplex reports EAFNOSUPPORT when starting up on Mac OSX which means
"Address family not supported by protocol family".
The issue is that in netplex_controller.ml/start_containers you are
doing
let (fd_clnt, fd_srv) =
Unix.socketpair Unix.PF_UNIX Unix.SOCK_STREAM 0 in
let (sys_fd_clnt, sys_fd_srv) =
Unix.socketpair Unix.PF_UNIX Unix.SOCK_STREAM 0 in
i.e. creating Unix Domain sockets.
Later on in rpc_transport.ml/stream_rpc_multiplex_controller you are
doing
`Sockaddr(Unix.getsockname fd)
which passes, and
`Sockaddr(Unix.getpeername fd)
which fails with EAFNOSUPPORT.
A Ruby test, on the other hand, ran without a hitch:
irb(main):001:0> require 'socket'
=> true
irb(main):002:0> x = Socket.pair Socket::PF_UNIX, Socket::SOCK_STREAM, 0
=> [#<Socket:0x7daa4>, #<Socket:0x7dab8>]
irb(main):003:0> x.each { |sock| sock.getpeername }
=> [#<Socket:0x7daa4>, #<Socket:0x7dab8>]
Thanks, Joel
--
http://wagerlabs.com/
next reply other threads:[~2007-05-05 12:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 12:40 Joel Reymont [this message]
2007-05-05 12:50 ` Joel Reymont
2007-05-05 12:57 ` [Caml-list] " Richard Jones
2007-05-05 14:00 ` Joel Reymont
2007-05-05 13:53 ` Mac OSX getsocketpair/getsockname and IPv6 Joel Reymont
2007-05-05 14:13 ` Serious bug in the OCaml FFI? Joel Reymont
2007-05-05 14:56 ` [Caml-list] " Olivier Andrieu
2007-05-05 15:24 ` Joel Reymont
2007-05-05 14:31 ` Mac OSX getsocketpair/getsockname and IPv6 Joel Reymont
2007-05-05 15:16 ` Solved! (was Re: Mac OSX getsocketpair/getsockname and IPv6) Joel Reymont
2007-05-06 10:05 ` [Caml-list] " Gerd Stolpmann
2007-05-28 17:08 ` Paul Snively
2007-05-05 14:46 ` Mac OSX getsocketpair/getsockname and IPv6 Joel Reymont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=71B2C4B5-3ECB-450F-B015-3C5EAB90855F@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@inria.fr \
--cc=gerd@gerd-stolpmann.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox