<sect1 id="net-common-tcpip-manpages-getdomainname">
<title>getdomainname</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-gethostname">
<title>gethostname</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-byteorder">
<title>byteorder</title>
<screen>
-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,
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
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
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
<sect1 id="net-common-tcpip-manpages-ethers">
<title>ethers</title>
<screen>
-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,
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.
<sect1 id="net-common-tcpip-manpages-getaddrinfo">
<title>getaddrinfo</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-gethostbyname">
<title>gethostbyname</title>
<screen>
-GETHOSTBYNAME(3) System Library Functions Manual GETHOSTBYNAME(3)
+GETHOSTBYNAME(3) BSD Library Functions Manual GETHOSTBYNAME(3)
NAME
gethostbyname, gethostbyname2, gethostbyaddr, gethostent, sethostent,
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.
<sect1 id="net-common-tcpip-manpages-getifaddrs">
<title>getifaddrs</title>
<screen>
-GETIFADDRS(3) System Library Functions Manual GETIFADDRS(3)
+GETIFADDRS(3) BSD Library Functions Manual GETIFADDRS(3)
NAME
getifaddrs - get interface addresses
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
</screen>
</sect1>
<sect1 id="net-common-tcpip-manpages-getnameinfo">
<title>getnameinfo</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-getnetent">
<title>getnetent</title>
<screen>
-GETNETENT(3) System Library Functions Manual GETNETENT(3)
+GETNETENT(3) BSD Library Functions Manual GETNETENT(3)
NAME
getnetent, getnetbyaddr, getnetbyname, setnetent, endnetent - get network
<sect1 id="net-common-tcpip-manpages-getprotoent">
<title>getprotoent</title>
<screen>
-GETPROTOENT(3) System Library Functions Manual GETPROTOENT(3)
+GETPROTOENT(3) BSD Library Functions Manual GETPROTOENT(3)
NAME
getprotoent, getprotobynumber, getprotobyname, setprotoent, endprotoent -
<sect1 id="net-common-tcpip-manpages-getrrsetbyname">
<title>getrrsetbyname</title>
<screen>
-GETRRSETBYNAME(3) System Library Functions Manual GETRRSETBYNAME(3)
+GETRRSETBYNAME(3) BSD Library Functions Manual GETRRSETBYNAME(3)
NAME
getrrsetbyname - retrieve DNS records
<sect1 id="net-common-tcpip-manpages-getservent">
<title>getservent</title>
<screen>
-GETSERVENT(3) System Library Functions Manual GETSERVENT(3)
+GETSERVENT(3) BSD Library Functions Manual GETSERVENT(3)
NAME
getservent, getservbyport, getservbyname, setservent, endservent - get
<sect1 id="net-common-tcpip-manpages-if-nametoindex">
<title>if_nametoindex</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-inet">
<title>inet</title>
<screen>
-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,
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-
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
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
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).
<sect1 id="net-common-tcpip-manpages-inet6-option-space">
<title>inet6_option_space</title>
<screen>
-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,
<sect1 id="net-common-tcpip-manpages-inet6-rthdr-space">
<title>inet6_rthdr_space</title>
<screen>
-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,
<sect1 id="net-common-tcpip-manpages-inet-net">
<title>inet_net</title>
<screen>
-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-
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).
<sect1 id="net-common-tcpip-manpages-ipx">
<title>ipx</title>
<screen>
-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
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
<sect1 id="net-common-tcpip-manpages-iso-addr">
<title>iso_addr</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-link-addr">
<title>link_addr</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-net-addrcmp">
<title>net_addrcmp</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-ns">
<title>ns</title>
<screen>
-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
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
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
<sect1 id="net-common-tcpip-manpages-resolver">
<title>resolver</title>
<screen>
-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,
<sect1 id="net-common-tcpip-manpages-accept">
<title>accept</title>
<screen>
-ACCEPT(2) System Calls Manual ACCEPT(2)
+ACCEPT(2) BSD System Calls Manual ACCEPT(2)
NAME
accept - accept a connection on a socket
<sect1 id="net-common-tcpip-manpages-bind">
<title>bind</title>
<screen>
-BIND(2) System Calls Manual BIND(2)
+BIND(2) BSD System Calls Manual BIND(2)
NAME
bind - bind a name to a socket
<sect1 id="net-common-tcpip-manpages-connect">
<title>connect</title>
<screen>
-CONNECT(2) System Calls Manual CONNECT(2)
+CONNECT(2) BSD System Calls Manual CONNECT(2)
NAME
connect - initiate a connection on a socket
<sect1 id="net-common-tcpip-manpages-getpeername">
<title>getpeername</title>
<screen>
-GETPEERNAME(2) System Calls Manual GETPEERNAME(2)
+GETPEERNAME(2) BSD System Calls Manual GETPEERNAME(2)
NAME
getpeername - get name of connected peer
<sect1 id="net-common-tcpip-manpages-getsockname">
<title>getsockname</title>
<screen>
-GETSOCKNAME(2) System Calls Manual GETSOCKNAME(2)
+GETSOCKNAME(2) BSD System Calls Manual GETSOCKNAME(2)
NAME
getsockname - get socket name
<sect1 id="net-common-tcpip-manpages-getsockopt">
<title>getsockopt</title>
<screen>
-GETSOCKOPT(2) System Calls Manual GETSOCKOPT(2)
+GETSOCKOPT(2) BSD System Calls Manual GETSOCKOPT(2)
NAME
getsockopt, setsockopt - get and set options on sockets
<sect1 id="net-common-tcpip-manpages-ioctl">
<title>ioctl</title>
<screen>
-IOCTL(2) System Calls Manual IOCTL(2)
+IOCTL(2) BSD System Calls Manual IOCTL(2)
NAME
ioctl - control device
<sect1 id="net-common-tcpip-manpages-poll">
<title>poll</title>
<screen>
-POLL(2) System Calls Manual POLL(2)
+POLL(2) BSD System Calls Manual POLL(2)
NAME
poll - synchronous I/O multiplexing
<sect1 id="net-common-tcpip-manpages-select">
<title>select</title>
<screen>
-SELECT(2) System Calls Manual SELECT(2)
+SELECT(2) BSD System Calls Manual SELECT(2)
NAME
select - synchronous I/O multiplexing
<sect1 id="net-common-tcpip-manpages-send">
<title>send</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-shutdown">
<title>shutdown</title>
<screen>
-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
<sect1 id="net-common-tcpip-manpages-socket">
<title>socket</title>
<screen>
-SOCKET(2) System Calls Manual SOCKET(2)
+SOCKET(2) BSD System Calls Manual SOCKET(2)
NAME
socket - create an endpoint for communication
HISTORY
The socket() function call appeared in 4.2BSD.
-BSD June 4, 1993 BSD
- </screen>
- </sect1>
-
- <sect1 id="net-common-tcpip-manpages-socketpair">
- <title>socketpair</title>
- <screen>
-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
</screen>
</sect1>
projects / karo-tx-redboot.git / blobdiff