# HG changeset patch # User asl # Date 1129204682 0 # Node ID 2ae48600be8b20e6facd889ef7536610af89688f # Parent cfec912002f39e8041ef9e5c1d431b35b7867acd * docs/manpages/sys/socketpair.2: Removed this man page since socketpair(2) is not supported. diff --git a/packages/net/common/current/ChangeLog b/packages/net/common/current/ChangeLog --- a/packages/net/common/current/ChangeLog +++ b/packages/net/common/current/ChangeLog @@ -1,3 +1,8 @@ +2005-10-13 Andrew Lunn + + * docs/manpages/sys/socketpair.2: Removed this man page since + socketpair(2) is not supported. + 2005-09-16 Andrew Lunn * tests/server_test.c: use socklen_t. diff --git a/packages/net/common/current/doc/manpages/sys/socketpair.2 b/packages/net/common/current/doc/manpages/sys/socketpair.2 deleted file mode 100644 --- a/packages/net/common/current/doc/manpages/sys/socketpair.2 +++ /dev/null @@ -1,109 +0,0 @@ -.\" $OpenBSD: socketpair.2,v 1.10 1999/07/06 18:21:04 deraadt Exp $ -.\" $NetBSD: socketpair.2,v 1.5 1995/02/27 12:38:00 cgd Exp $ -.\" -.\" Copyright (c) 1983, 1991, 1993 -.\" The Regents of the University of California. All rights reserved. -.\" -.\" Redistribution and use in source and binary forms, with or without -.\" modification, are permitted provided that the following conditions -.\" are met: -.\" 1. Redistributions of source code must retain the above copyright -.\" notice, this list of conditions and the following disclaimer. -.\" 2. Redistributions in binary form must reproduce the above copyright -.\" notice, this list of conditions and the following disclaimer in the -.\" documentation and/or other materials provided with the distribution. -.\" 3. All advertising materials mentioning features or use of this software -.\" must display the following acknowledgement: -.\" This product includes software developed by the University of -.\" California, Berkeley and its contributors. -.\" 4. Neither the name of the University nor the names of its contributors -.\" may be used to endorse or promote products derived from this software -.\" without specific prior written permission. -.\" -.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND -.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE -.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE -.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE -.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL -.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS -.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) -.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT -.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY -.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF -.\" SUCH DAMAGE. -.\" -.\" @(#)socketpair.2 8.1 (Berkeley) 6/4/93 -.\" -.Dd June 4, 1993 -.Dt SOCKETPAIR 2 -.Os -.Sh NAME -.Nm socketpair -.Nd create a pair of connected sockets -.Sh SYNOPSIS -.Fd #include -.Fd #include -.Ft int -.Fn socketpair "int d" "int type" "int protocol" "int *sv" -.Sh DESCRIPTION -The -.Fn socketpair -call creates an unnamed pair of connected sockets in -the specified domain -.Fa d , -of the specified -.Fa type , -and using the optionally specified -.Fa protocol . -The descriptors used in referencing the new sockets -are returned in -.Fa sv Ns [0] -and -.Fa sv Ns [1] . -The two sockets are indistinguishable. -.Sh RETURN VALUES -A 0 is returned if the call succeeds, \-1 if it fails. -.Sh ERRORS -The call succeeds unless: -.Bl -tag -width Er -.It Bq Er EMFILE -Too many descriptors are in use by this process. -.It Bq Er EAFNOSUPPORT -The specified address family is not supported on this machine. -.It Bq Er EPROTONOSUPPORT -The specified protocol is not supported on this machine. -.It Bq Er EOPNOTSUPP -The specified protocol does not support creation of socket pairs. -.It Bq Er EFAULT -The address -.Fa sv -does not specify a valid part of the -process address space. -.It Bq Er ENFILE -The system file table is full. -.El -.Sh SEE ALSO -.Xr pipe 2 , -.Xr read 2 , -.Xr write 2 -.Sh BUGS -This call is currently implemented only for the -.Tn LOCAL -domain. -Many operating systems only accept a -.Ar protocol -of -.Ev PF_UNSPEC , -so that should be used instead of -.Ev PF_LOCAL -for maximal portability. -.Sh STANDARDS -The -.Fn socketpair -function conforms to -.St -xpg4.2 . -.Sh HISTORY -The -.Fn socketpair -function call appeared in -.Bx 4.2 . diff --git a/packages/net/common/current/doc/tcpip-manpages.sgml b/packages/net/common/current/doc/tcpip-manpages.sgml --- a/packages/net/common/current/doc/tcpip-manpages.sgml +++ b/packages/net/common/current/doc/tcpip-manpages.sgml @@ -11,7 +11,7 @@ getdomainname -GETDOMAINNAME(3) System Library Functions Manual GETDOMAINNAME(3) +GETDOMAINNAME(3) BSD Library Functions Manual GETDOMAINNAME(3) NAME getdomainname, setdomainname - get/set YP domain name of current host @@ -69,7 +69,7 @@ BSD May 6, gethostname -GETHOSTNAME(3) System Library Functions Manual GETHOSTNAME(3) +GETHOSTNAME(3) BSD Library Functions Manual GETHOSTNAME(3) NAME gethostname, sethostname - get/set name of current host @@ -131,7 +131,7 @@ BSD June 4, byteorder -BYTEORDER(3) System Library Functions Manual BYTEORDER(3) +BYTEORDER(3) BSD Library Functions Manual BYTEORDER(3) NAME htonl, htons, ntohl, ntohs, htobe32, htobe16, betoh32, betoh16, htole32, @@ -199,11 +199,11 @@ DESCRIPTION be Big-endian (most significant byte first). le Little-endian (least significant byte first). - One of the specified orderings must be `h'. {size} will take these + One of the specified orderings must be 'h'. {size} will take these forms: - l Long (32-bit, used in conjunction with forms involving `n'). - s Short (16-bit, used in conjunction with forms involving `n'). + l Long (32-bit, used in conjunction with forms involving 'n'). + s Short (16-bit, used in conjunction with forms involving 'n'). 16 16-bit. 32 @@ -211,8 +211,8 @@ DESCRIPTION The swap functions are of the form: swap{size}. - Names involving `n' convert quantities between network byte order and - host byte order. The last letter (`s' or `l') is a mnemonic for the tra- + Names involving 'n' convert quantities between network byte order and + host byte order. The last letter ('s' or 'l') is a mnemonic for the tra- ditional names for such quantities, short and long, respectively. Today, the C concept of short and long integers need not coincide with this tra- ditional misunderstanding. On machines which have a byte order which is @@ -225,7 +225,7 @@ DESCRIPTION macros. The routines mentioned above which have either {src-order} or {dst-order} - set to `n' are most often used in conjunction with Internet addresses and + set to 'n' are most often used in conjunction with Internet addresses and ports as returned by gethostbyname(3) and getservent(3). SEE ALSO @@ -246,7 +246,7 @@ BSD June 4, ethers -ETHERS(3) System Library Functions Manual ETHERS(3) +ETHERS(3) BSD Library Functions Manual ETHERS(3) NAME ether_aton, ether_ntoa, ether_addr, ether_ntohost, ether_hostton, @@ -293,7 +293,7 @@ DESCRIPTION address into the structure passed. Both functions return zero if they find the requested host name or address, and -1 if not. - Each call reads /etc/ethers from the beginning; if a `+' appears alone on + Each call reads /etc/ethers from the beginning; if a '+' appears alone on a line in the file, then ether_hostton() will consult the ethers.byname YP map, and ether_ntohost() will consult the ethers.byaddr YP map. @@ -326,7 +326,7 @@ BSD December getaddrinfo -GETADDRINFO(3) System Library Functions Manual GETADDRINFO(3) +GETADDRINFO(3) BSD Library Functions Manual GETADDRINFO(3) NAME getaddrinfo, freeaddrinfo, gai_strerror - nodename-to-address translation @@ -625,7 +625,7 @@ BSD May 25, gethostbyname -GETHOSTBYNAME(3) System Library Functions Manual GETHOSTBYNAME(3) +GETHOSTBYNAME(3) BSD Library Functions Manual GETHOSTBYNAME(3) NAME gethostbyname, gethostbyname2, gethostbyaddr, gethostent, sethostent, @@ -714,7 +714,7 @@ DESCRIPTION The herror() function prints an error message describing the failure. If its argument string is non-null, it is prepended to the message string - and separated from it by a colon (`:') and a space. The error message is + and separated from it by a colon (':') and a space. The error message is printed with a trailing newline. The contents of the error message is the same as that returned by hstrerror() with argument h_errno. @@ -782,7 +782,7 @@ BSD March 13 getifaddrs -GETIFADDRS(3) System Library Functions Manual GETIFADDRS(3) +GETIFADDRS(3) BSD Library Functions Manual GETIFADDRS(3) NAME getifaddrs - get interface addresses @@ -873,14 +873,14 @@ HISTORY The getifaddrs() function first appeared in BSDI BSD/OS. The function is supplied on OpenBSD since OpenBSD 2.7. -BSD February 24, 2003 BSD +BSD October 13, 2005 BSD getnameinfo -GETNAMEINFO(3) System Library Functions Manual GETNAMEINFO(3) +GETNAMEINFO(3) BSD Library Functions Manual GETNAMEINFO(3) NAME getnameinfo - address-to-nodename translation in protocol-independent @@ -1053,7 +1053,7 @@ BSD May 25, getnetent -GETNETENT(3) System Library Functions Manual GETNETENT(3) +GETNETENT(3) BSD Library Functions Manual GETNETENT(3) NAME getnetent, getnetbyaddr, getnetbyname, setnetent, endnetent - get network @@ -1143,7 +1143,7 @@ BSD March 13 getprotoent -GETPROTOENT(3) System Library Functions Manual GETPROTOENT(3) +GETPROTOENT(3) BSD Library Functions Manual GETPROTOENT(3) NAME getprotoent, getprotobynumber, getprotobyname, setprotoent, endprotoent - @@ -1226,7 +1226,7 @@ BSD June 4, getrrsetbyname -GETRRSETBYNAME(3) System Library Functions Manual GETRRSETBYNAME(3) +GETRRSETBYNAME(3) BSD Library Functions Manual GETRRSETBYNAME(3) NAME getrrsetbyname - retrieve DNS records @@ -1325,7 +1325,7 @@ BSD Oct 18, getservent -GETSERVENT(3) System Library Functions Manual GETSERVENT(3) +GETSERVENT(3) BSD Library Functions Manual GETSERVENT(3) NAME getservent, getservbyport, getservbyname, setservent, endservent - get @@ -1413,7 +1413,7 @@ BSD January 1 if_nametoindex -IF_NAMETOINDEX(3) System Library Functions Manual IF_NAMETOINDEX(3) +IF_NAMETOINDEX(3) BSD Library Functions Manual IF_NAMETOINDEX(3) NAME if_nametoindex, if_indextoname, if_nameindex, if_freenameindex - convert @@ -1487,7 +1487,7 @@ BSD May 21, inet -INET(3) System Library Functions Manual INET(3) +INET(3) BSD Library Functions Manual INET(3) NAME inet_addr, inet_aton, inet_lnaof, inet_makeaddr, inet_netof, @@ -1528,7 +1528,7 @@ SYNOPSIS DESCRIPTION The routines inet_aton(), inet_addr() and inet_network() interpret char- - acter strings representing numbers expressed in the Internet standard `.' + acter strings representing numbers expressed in the Internet standard '.' notation. The inet_pton() function converts a presentation format address (that is, printable form as held in a character string) to net- work format (usually a struct in_addr or some other internal binary rep- @@ -1549,7 +1549,7 @@ DESCRIPTION NULL if a system error occurs (in which case, errno will have been set), or it returns a pointer to the destination string. The routine inet_ntoa() takes an Internet address and returns an ASCII string repre- - senting the address in `.' notation. The routine inet_makeaddr() takes + senting the address in '.' notation. The routine inet_makeaddr() takes an Internet network number and a local network address and constructs an Internet address from it. The routines inet_netof() and inet_lnaof() break apart Internet host addresses, returning the network number and @@ -1560,7 +1560,7 @@ DESCRIPTION as machine format integer values. INTERNET ADDRESSES (IP VERSION 4) - Values specified using the `.' notation take one of the following forms: + Values specified using the '.' notation take one of the following forms: a.b.c.d a.b.c @@ -1588,7 +1588,7 @@ INTERNET ADDRESSES (IP VERSION 4) When only one part is given, the value is stored directly in the network address without any byte rearrangement. - All numbers supplied as ``parts'' in a `.' notation may be decimal, + All numbers supplied as ``parts'' in a '.' notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; other- wise, the number is interpreted as decimal). @@ -1691,7 +1691,7 @@ BSD June 18 inet6_option_space -INET6_OPTION_SPACE(3) System Library Functions Manual INET6_OPTION_SPACE(3) +INET6_OPTION_SPACE(3) BSD Library Functions Manual INET6_OPTION_SPACE(3) NAME inet6_option_space, inet6_option_init, inet6_option_append, @@ -1891,7 +1891,7 @@ BSD December inet6_rthdr_space -INET6_RTHDR_SPACE(3) System Library Functions Manual INET6_RTHDR_SPACE(3) +INET6_RTHDR_SPACE(3) BSD Library Functions Manual INET6_RTHDR_SPACE(3) NAME inet6_rthdr_space, inet6_rthdr_init, inet6_rthdr_add, @@ -2080,7 +2080,7 @@ BSD December inet_net -INET_NET(3) System Library Functions Manual INET_NET(3) +INET_NET(3) BSD Library Functions Manual INET_NET(3) NAME inet_net_ntop, inet_net_pton - Internet network number manipulation rou- @@ -2147,7 +2147,7 @@ NETWORK NUMBERS (IP VERSION 4) When only one part is given, the value is stored directly in the Internet network number without any byte rearrangement. - All numbers supplied as ``parts'' in a `.' notation may be decimal, + All numbers supplied as ``parts'' in a '.' notation may be decimal, octal, or hexadecimal, as specified in the C language (i.e., a leading 0x or 0X implies hexadecimal; otherwise, a leading 0 implies octal; other- wise, the number is interpreted as decimal). @@ -2166,7 +2166,7 @@ BSD June 18 ipx -IPX(3) System Library Functions Manual IPX(3) +IPX(3) BSD Library Functions Manual IPX(3) NAME ipx_addr, ipx_ntoa - IPX address conversion routines @@ -2191,21 +2191,21 @@ DESCRIPTION Trailing zero fields are suppressed, and each number is printed in hex- adecimal, in a format suitable for input to ipx_addr(). Any fields lack- - ing super-decimal digits will have a trailing `H' appended. + ing super-decimal digits will have a trailing 'H' appended. An effort has been made to ensure that ipx_addr() be compatible with most formats in common use. It will first separate an address into 1 to 3 - fields using a single delimiter chosen from period (`.'), colon (`:'), or - pound-sign (`#'). Each field is then examined for byte separators (colon + fields using a single delimiter chosen from period ('.'), colon (':'), or + pound-sign ('#'). Each field is then examined for byte separators (colon or period). If there are byte separators, each subfield separated is taken to be a small hexadecimal number, and the entirety is taken as a network-byte-ordered quantity to be zero extended in the high-network- order bytes. Next, the field is inspected for hyphens, in which case the field is assumed to be a number in decimal notation with hyphens separat- ing the millenia. Next, the field is assumed to be a number: It is - interpreted as hexadecimal if there is a leading `0x' (as in C), a trail- - ing `H' (as in Mesa), or there are any super-decimal digits present. It - is interpreted as octal is there is a leading `0' and there are no super- + interpreted as hexadecimal if there is a leading '0x' (as in C), a trail- + ing 'H' (as in Mesa), or there are any super-decimal digits present. It + is interpreted as octal is there is a leading '0' and there are no super- octal digits. Otherwise, it is converted as a decimal number. RETURN VALUES @@ -2229,7 +2229,7 @@ BSD June 4, iso_addr -ISO_ADDR(3) System Library Functions Manual ISO_ADDR(3) +ISO_ADDR(3) BSD Library Functions Manual ISO_ADDR(3) NAME iso_addr, iso_ntoa - network address conversion routines for Open System @@ -2289,7 +2289,7 @@ BSD June 4, link_addr -LINK_ADDR(3) System Library Functions Manual LINK_ADDR(3) +LINK_ADDR(3) BSD Library Functions Manual LINK_ADDR(3) NAME link_addr, link_ntoa - elementary address specification routines for link @@ -2352,7 +2352,7 @@ BSD July 28 net_addrcmp -NET_ADDRCMP(3) System Library Functions Manual NET_ADDRCMP(3) +NET_ADDRCMP(3) BSD Library Functions Manual NET_ADDRCMP(3) NAME net_addrcmp - compare socket address structures @@ -2393,7 +2393,7 @@ BSD July 3, ns -NS(3) System Library Functions Manual NS(3) +NS(3) BSD Library Functions Manual NS(3) NAME ns_addr, ns_ntoa - Xerox NS(tm) address conversion routines @@ -2419,13 +2419,13 @@ DESCRIPTION Trailing zero fields are suppressed, and each number is printed in hex- adecimal, in a format suitable for input to ns_addr(). Any fields lack- - ing super-decimal digits will have a trailing `H' appended. + ing super-decimal digits will have a trailing 'H' appended. Unfortunately, no universal standard exists for representing XNS addresses. An effort has been made to ensure that ns_addr() be compati- ble with most formats in common use. It will first separate an address - into 1 to 3 fields using a single delimiter chosen from period (`.'), - colon (`:'), or pound-sign `#'. Each field is then examined for byte + into 1 to 3 fields using a single delimiter chosen from period ('.'), + colon (':'), or pound-sign '#'. Each field is then examined for byte separators (colon or period). If there are byte separators, each sub- field separated is taken to be a small hexadecimal number, and the entirety is taken as a network-byte-ordered quantity to be zero extended @@ -2433,9 +2433,9 @@ DESCRIPTION hyphens, in which case the field is assumed to be a number in decimal notation with hyphens separating the millenia. Next, the field is assumed to be a number: It is interpreted as hexadecimal if there is a - leading `0x' (as in C), a trailing `H' (as in Mesa), or there are any + leading '0x' (as in C), a trailing 'H' (as in Mesa), or there are any super-decimal digits present. It is interpreted as octal is there is a - leading `0' and there are no super-octal digits. Otherwise, it is con- + leading '0' and there are no super-octal digits. Otherwise, it is con- verted as a decimal number. RETURN VALUES @@ -2459,7 +2459,7 @@ BSD June 4, resolver -RESOLVER(3) System Library Functions Manual RESOLVER(3) +RESOLVER(3) BSD Library Functions Manual RESOLVER(3) NAME res_query, res_search, res_mkquery, res_send, res_init, dn_comp, @@ -2623,7 +2623,7 @@ BSD June 4, accept -ACCEPT(2) System Calls Manual ACCEPT(2) +ACCEPT(2) BSD System Calls Manual ACCEPT(2) NAME accept - accept a connection on a socket @@ -2714,7 +2714,7 @@ BSD February bind -BIND(2) System Calls Manual BIND(2) +BIND(2) BSD System Calls Manual BIND(2) NAME bind - bind a name to a socket @@ -2799,7 +2799,7 @@ BSD February connect -CONNECT(2) System Calls Manual CONNECT(2) +CONNECT(2) BSD System Calls Manual CONNECT(2) NAME connect - initiate a connection on a socket @@ -2902,7 +2902,7 @@ BSD February getpeername -GETPEERNAME(2) System Calls Manual GETPEERNAME(2) +GETPEERNAME(2) BSD System Calls Manual GETPEERNAME(2) NAME getpeername - get name of connected peer @@ -2977,7 +2977,7 @@ BSD July 17 getsockname -GETSOCKNAME(2) System Calls Manual GETSOCKNAME(2) +GETSOCKNAME(2) BSD System Calls Manual GETSOCKNAME(2) NAME getsockname - get socket name @@ -3064,7 +3064,7 @@ BSD July 17 getsockopt -GETSOCKOPT(2) System Calls Manual GETSOCKOPT(2) +GETSOCKOPT(2) BSD System Calls Manual GETSOCKOPT(2) NAME getsockopt, setsockopt - get and set options on sockets @@ -3251,7 +3251,7 @@ BSD February ioctl -IOCTL(2) System Calls Manual IOCTL(2) +IOCTL(2) BSD System Calls Manual IOCTL(2) NAME ioctl - control device @@ -3309,7 +3309,7 @@ BSD December poll -POLL(2) System Calls Manual POLL(2) +POLL(2) BSD System Calls Manual POLL(2) NAME poll - synchronous I/O multiplexing @@ -3424,7 +3424,7 @@ BSD December select -SELECT(2) System Calls Manual SELECT(2) +SELECT(2) BSD System Calls Manual SELECT(2) NAME select - synchronous I/O multiplexing @@ -3566,7 +3566,7 @@ BSD March 25 send -SEND(2) System Calls Manual SEND(2) +SEND(2) BSD System Calls Manual SEND(2) NAME send, sendto, sendmsg - send a message from a socket @@ -3699,7 +3699,7 @@ BSD July 28 shutdown -SHUTDOWN(2) System Calls Manual SHUTDOWN(2) +SHUTDOWN(2) BSD System Calls Manual SHUTDOWN(2) NAME shutdown - shut down part of a full-duplex connection @@ -3747,7 +3747,7 @@ BSD June 4, socket -SOCKET(2) System Calls Manual SOCKET(2) +SOCKET(2) BSD System Calls Manual SOCKET(2) NAME socket - create an endpoint for communication @@ -3884,68 +3884,6 @@ BSD June 4, - - socketpair - -SOCKETPAIR(2) System Calls Manual SOCKETPAIR(2) - -NAME - socketpair - create a pair of connected sockets - -SYNOPSIS - #include <sys/types.h> - #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 spec- - ified protocol. The descriptors used in referencing the new sockets are - returned in sv[0] and sv[1]. The two sockets are indistinguishable. - -RETURN VALUES - A 0 is returned if the call succeeds, -1 if it fails. - -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. - - [ENFILE] The system file table is full. - -SEE ALSO - pipe(2), read(2), write(2) - -BUGS - This call is currently implemented only for the LOCAL domain. Many oper- - ating systems only accept a protocol of PF_UNSPEC, so that should be used - instead of PF_LOCAL for maximal portability. - -STANDARDS - The socketpair() function conforms to X/Open Portability Guide Issue 4.2 - (``XPG4.2''). - -HISTORY - The socketpair() function call appeared in 4.2BSD. - -BSD June 4, 1993 BSD - - -