You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 4, 2018. It is now read-only.
The method uv_pipe_connect() takes the pipe name as a null-terminated string. This unfortunately prevents you from specifying abstract unix socket addresses. An abstract unix socket addres for "/tmp/foo" is specified as "\x00/tmp/foo" so exactly the same but starting with a null byte.
The abstract namespace is used by e.g. the D-BUS session bus which is where I need this for.
The text was updated successfully, but these errors were encountered:
Abstract socket addresses are a Linux-ism, I don't think we want to support that. If you need that functionality, you can create a socket manually and pass it to uv_pipe_open().
No problem. FWIW, on Linux, as long as you turn on the O_NONBLOCK flag on the socket, you don't have to worry about dealing with EINPROGRESS: either the connect() syscall succeeds or it fails with EAGAIN (when the server's backlog is full) but there never is a 'partially done' state like there is with TCP sockets.
The method
uv_pipe_connect()
takes the pipe name as a null-terminated string. This unfortunately prevents you from specifying abstract unix socket addresses. An abstract unix socket addres for"/tmp/foo"
is specified as"\x00/tmp/foo"
so exactly the same but starting with a null byte.The abstract namespace is used by e.g. the D-BUS session bus which is where I need this for.
The text was updated successfully, but these errors were encountered: