Lines Matching +full:c +full:- +full:family +full:- +full:name

2 .\"  Copyright (c) 1992, X/Open Company Limited  All Rights Reserved  Portions
3 .\" Copyright (c) 1999, Sun Microsystems, Inc. All Rights Reserved
6 .\" The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase "this text" refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in the Sun OS Reference Manual, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html.
10 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
12 .SH NAME
13 socket \- create an endpoint for communication
17 \fBcc\fR [ \fIflag\fR ... ] \fIfile\fR ... \fB-lxnet\fR [ \fIlibrary\fR ... ]
64 system are implementation-dependent. Possible socket types include:
71 Provides sequenced, reliable, bidirectional, connection-mode byte streams, and
72 may provide a transmission mechanism for out-of-band data.
81 Provides datagrams, which are connectionless-mode, unreliable messages of fixed
91 Provides sequenced, reliable, bidirectional, connection-mode transmission path
100 If the \fIprotocol\fR argument is non-zero, it must specify a protocol that is
101 supported by the address family. The protocols supported by the system are
102 implementation-dependent.
142 The \fIdomain\fR argument specifies the address family used in the
144 implementation-dependent.
149 address family supports. The documentation for specific protocols specify
153 The application can determine if an address family is supported by trying to
159 socket file descriptor. Otherwise a value of \fB-1\fR is returned and
171 The implementation does not support the specified address family.
198 The protocol is not supported by the address family, or the protocol is not
260 c | c
266 MT-Level MT-Safe