2 .\" Copyright (c) 2008, Sun Microsystems, Inc. All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" 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]
6 .TH SOCONFIG 1M "Apr 12, 2014"
8 soconfig \- configure transport providers for use by sockets
12 \fB/sbin/soconfig\fR \fB-d\fR \fIdir\fR
17 \fB/sbin/soconfig\fR \fB-f\fR \fIfile\fR
22 \fB/sbin/soconfig\fR \fIfamily\fR \fItype\fR \fIprotocol\fR [\fImodule\fR | \fIpath\fR]
28 The \fBsoconfig\fR utility configures the transport provider driver for use
29 with sockets. It specifies how the family, type, and protocol parameters in the
30 \fBsocket\fR(3SOCKET) call are mapped to the name of a transport provider such
31 as \fB/dev/tcp\fR. This utility can be used to add an additional mapping or
32 remove a previous mapping.
35 The \fBinit\fR(1M) utility uses \fBsoconfig\fR with the \fBsock2path.d\fR(4)
36 directory during the booting sequence.
40 The following options are supported:
44 \fB\fB-d\fR \fIdir\fR\fR
47 Set up the \fBsoconfig\fR configuration for each driver
48 according to the information stored in the
55 \fB\fB-f\fR \fIfile\fR\fR
58 Set up the \fBsoconfig\fR configuration for each driver according to the
59 information stored in \fIfile\fR. A \fBsoconfig\fR file consists of lines of at
60 least the first three fields listed below, separated by spaces:
62 \fIfamily type protocol [module | path]\fR
64 These fields are described in the \fBOPERANDS\fR section below.
66 An example of \fIfile\fR can be found in the \fBEXAMPLES\fR section below.
72 The following operands are supported:
79 The protocol family as listed in the \fB/usr/include/sys/socket.h\fR file,
80 expressed as an integer.
89 The socket type as listed in the \fB/usr/include/sys/socket.h\fR file,
90 expressed as an integer.
99 The protocol number as specified in the family-specific \fBinclude\fR file,
100 expressed as an integer. For example, for \fBAF_INET\fR this number is
101 specified in \fB/usr/include/netinet/in.h\fR. An unspecified protocol number is
102 denoted with the value zero.
108 \fB\fImodule\fR | \fIpath\fR\fR
111 The module name or path name of a device that corresponds to the transport
112 provider, such as \fBtcp\fR or \fB/dev/tcp\fR. Modules must reside in
113 \fBkernel/socketmod\fR. A device name must begin with \fB/dev\fR. If this
114 parameter is specified, the configuration will be added for the specified
115 family, type, and protocol. If this parameter is not specified, the
116 configuration will be removed.
121 \fBExample 1 \fRUsing \fBsoconfig\fR
124 The following example sets up a module for family \fBAF_INET\fR and type
130 example# \fBsoconfig 2 2 0 tcp\fR
137 The following example sets up \fB/dev/tcp\fR for family \fBAF_INET\fR and type
143 example# \fBsoconfig 2 2 0 /dev/tcp\fR
150 The following is a sample file used with the \fB-f\fR option. Comment lines
151 begin with a hash mark (\fB#\fR):
156 # Family Type Protocol Module | Path
175 \fB\fB/etc/sock2path.d\fR\fR
178 Directory containing files with mappings from
179 sockets to transport providers.
185 \fBinit\fR(1M), \fBsock2path.d\fR(4), \fBattributes\fR(5)
188 \fINetwork Interface Guide\fR