SOCKETPAIR(2) BSD System Calls Manual SOCKETPAIR(2)NAME
socketpair -- create a pair of connected sockets
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/socket.h>
int
socketpair(int d, int type, int protocol, int *sv);
DESCRIPTION
The socketpair() call creates an unnamed pair of connected sockets in the specified domain d, of the specified type, and using the optionally
specified protocol. The descriptors used in referencing the new sockets are returned in sv[0] and sv[1]. The two sockets are indistinguish-
able.
The type and protocol argument values are described in socket(2).
RETURN VALUES
A 0 is returned if the call succeeds, -1 if it fails.
ERRORS
The call succeeds unless:
[EAFNOSUPPORT] The specified address family is not supported on this machine.
[EFAULT] The address sv does not specify a valid part of the process address space.
[EMFILE] Too many descriptors are in use by this process.
[ENFILE] The system file table is full.
[EOPNOTSUPP] The specified protocol does not support creation of socket pairs.
[EPROTONOSUPPORT] The specified protocol is not supported on this machine.
SEE ALSO pipe(2), read(2), socket(2), write(2)HISTORY
The socketpair() function call appeared in 4.2BSD.
BUGS
This call is currently implemented only for the PF_LOCAL domain.
BSD June 24, 2011 BSD
Check Out this Related Man Page
SOCKETPAIR(2) BSD System Calls Manual SOCKETPAIR(2)NAME
socketpair -- create a pair of connected sockets
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <sys/types.h>
#include <sys/socket.h>
int
socketpair(int fd, int type, int protocol, int *sv);
DESCRIPTION
The socketpair() system call creates an unnamed pair of connected sockets in the specified domain fd, of the specified type, and using the
optionally specified protocol. The descriptors used in referencing the new sockets are returned in sv[0] and sv[1]. The two sockets are
indistinguishable.
The SOCK_CLOEXEC and SOCK_NONBLOCK flags in the type argument apply to both descriptors.
RETURN VALUES
The socketpair() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
cate the error.
ERRORS
The call succeeds unless:
[EMFILE] Too many descriptors are in use by this process.
[EAFNOSUPPORT] The specified address family is not supported on this machine.
[EPROTONOSUPPORT] The specified protocol is not supported on this machine.
[EOPNOTSUPP] The specified protocol does not support creation of socket pairs.
[EFAULT] The address sv does not specify a valid part of the process address space.
SEE ALSO pipe(2), read(2), socket(2), write(2)HISTORY
The socketpair() system call appeared in 4.2BSD.
BUGS
This call is currently implemented only for the UNIX domain.
BSD September 11, 2013 BSD
what is the difference to use socketpair and socket while socket programming
other than socket create a single socket,socketpair creates a pair of sockets (0 Replies)
For windows was pretty simple to redirect the std in a and out of a
child process for "cmd.exe " command prompt terminal to a socket using connected pipes passed to a new process in the STARTUPINFO structure.
BOOL b = ::CreatePipe((LPHANDLE)h_stdInRead,(LPHANDLE)hsdtInWriteTmp, &SecAttrib,... (1 Reply)
anyone and teach me how to save standard output to a file in a client/server socket. I know how to read them to the screen but i'm not quite sure how to save them to a file.
my read to screen file code:
memset(line, 0x0, LINE_ARRAY_SIZE);
while (recv(connectSocket, line, MAX_MSG, 0) >... (1 Reply)