socket.2 (108028) | socket.2 (108087) |
---|---|
1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" From: @(#)socket.2 8.1 (Berkeley) 6/4/93 | 1.\" Copyright (c) 1983, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. --- 16 unchanged lines hidden (view full) --- 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" From: @(#)socket.2 8.1 (Berkeley) 6/4/93 |
33.\" $FreeBSD: head/lib/libc/sys/socket.2 108028 2002-12-18 09:22:32Z ru $ | 33.\" $FreeBSD: head/lib/libc/sys/socket.2 108087 2002-12-19 09:40:28Z ru $ |
34.\" 35.Dd November 24, 1997 36.Dt SOCKET 2 37.Os 38.Sh NAME 39.Nm socket 40.Nd create an endpoint for communication 41.Sh LIBRARY --- 6 unchanged lines hidden (view full) --- 48.Sh DESCRIPTION 49The 50.Fn socket 51system call 52creates an endpoint for communication and returns a descriptor. 53.Pp 54The 55.Fa domain | 34.\" 35.Dd November 24, 1997 36.Dt SOCKET 2 37.Os 38.Sh NAME 39.Nm socket 40.Nd create an endpoint for communication 41.Sh LIBRARY --- 6 unchanged lines hidden (view full) --- 48.Sh DESCRIPTION 49The 50.Fn socket 51system call 52creates an endpoint for communication and returns a descriptor. 53.Pp 54The 55.Fa domain |
56parameter specifies a communications domain within which | 56argument specifies a communications domain within which |
57communication will take place; this selects the protocol family 58which should be used. 59These families are defined in the include file 60.Ao Pa sys/socket.h Ac . 61The currently understood formats are: 62.Pp 63.Bd -literal -offset indent -compact 64PF_LOCAL Host-internal protocols, formerly called PF_UNIX, --- 69 unchanged lines hidden (view full) --- 134.Dv SOCK_RAW , 135which is available only to the super-user, and 136.Dv SOCK_RDM , 137which is planned, 138but not yet implemented, are not described here. 139.Pp 140The 141.Fa protocol | 57communication will take place; this selects the protocol family 58which should be used. 59These families are defined in the include file 60.Ao Pa sys/socket.h Ac . 61The currently understood formats are: 62.Pp 63.Bd -literal -offset indent -compact 64PF_LOCAL Host-internal protocols, formerly called PF_UNIX, --- 69 unchanged lines hidden (view full) --- 134.Dv SOCK_RAW , 135which is available only to the super-user, and 136.Dv SOCK_RDM , 137which is planned, 138but not yet implemented, are not described here. 139.Pp 140The 141.Fa protocol |
142argument |
|
142specifies a particular protocol to be used with the socket. 143Normally only a single protocol exists to support a particular 144socket type within a given protocol family. However, it is possible 145that many protocols may exist, in which case a particular protocol 146must be specified in this manner. The protocol number to use is 147particular to the 148.Dq "communication domain" 149in which communication --- 157 unchanged lines hidden --- | 143specifies a particular protocol to be used with the socket. 144Normally only a single protocol exists to support a particular 145socket type within a given protocol family. However, it is possible 146that many protocols may exist, in which case a particular protocol 147must be specified in this manner. The protocol number to use is 148particular to the 149.Dq "communication domain" 150in which communication --- 157 unchanged lines hidden --- |