Allow passing of LISTENING TCP sockets
Final Release Note
WRITE /PASS
and WRITE /ACCEPT
allow also LISTENING TCP sockets to be passed from one process to another. Previously, only CONNECTED TCP sockets could be passed, and an attempt to pass a LISTENING TCP socket resulted in the WRITE /ACCEPT
command raising a GETSOCKNAMERR error. [#996 (closed)]
Description
Currently, one is able to pass LISTENING LOCAL sockets, CONNECTED LOCAL sockets and CONNECTED TCP sockets to another process using WRITE /PASS
and WRITE /ACCEPT
syntax (see https://docs.yottadb.com/ProgrammersGuide/ioproc.html#write-command for details).
But if one tries to pass LISTENING TCP sockets to another process, one gets the below error as part of the WRITE /ACCEPT
.
%YDB-E-GETSOCKNAMERR, Getting the socket name failed from getsockname(): (errno==107) Transport endpoint is not connected
Draft Release Note
WRITE /PASS
and WRITE /ACCEPT
allow also LISTENING TCP sockets to be passed from one process to another. Previously, only CONNECTED TCP sockets could be passed, and an attempt to pass a LISTENING TCP socket resulted in the WRITE /ACCEPT
command raising a GETSOCKNAMERR error.