1inetd.conf(4) File Formats inetd.conf(4)
2
6 inetd.conf - Internet servers database
7
9 /etc/inet/inetd.conf
10 /etc/inetd.conf
13
16 In the current release of the Solaris operating system, the inetd.conf
17 file is no longer directly used to configure inetd. The Solaris ser‐
18 vices which were formerly configured using this file are now configured
19 in the Service Management Facility (see smf(5)) using inetadm(1M). Any
20 records remaining in this file after installation or upgrade, or later
21 created by installing additional software, must be converted to smf(5)
22 services and imported into the SMF repository using inetconv(1M), oth‐
23 erwise the service will not be available.
24 For Solaris operating system releases prior to the current release
27 (such as Solaris 9), the inetd.conf file contains the list of servers
28 that inetd(1M) invokes when it receives an Internet request over a
29 socket. Each server entry is composed of a single line of the form:
30 service-name endpoint-type protocol wait-status uid server-program \
32 server-arguments
33 Fields are separated by either SPACE or TAB characters. A `#' (number
38 sign) indicates the beginning of a comment; characters up to the end of
39 the line are not interpreted by routines that search this file.
40 service-name The name of a valid service listed in the services
42 file. For RPC services, the value of the service-
43 name field consists of the RPC service name or pro‐
44 gram number, followed by a '/' (slash) and either a
45 version number or a range of version numbers, for
46 example, rstatd/2-4.
47 endpoint-type Can be one of:
50 stream for a stream socket
52 dgram for a datagram socket
55 raw for a raw socket
58 seqpacket for a sequenced packet socket
61 tli for all TLI endpoints
64 protocol A recognized protocol listed in the file
68 /etc/inet/protocols. For servers capable of sup‐
69 porting TCP and UDP over IPv6, the following proto‐
70 col types are also recognized:
71 o tcp6
73 o udp6
75 tcp6 and udp6 are not official protocols; accord‐
76 ingly, they are not listed in the /etc/inet/proto‐
77 cols file.
78 Here the inetd program uses an AF_INET6 type socket
80 endpoint. These servers can also handle incoming
81 IPv4 client requests in addition to IPv6 client
82 requests.
83 For RPC services, the field consists of the string
85 rpc followed by a '/' (slash) and either a '*'
86 (asterisk), one or more nettypes, one or more
87 netids, or a combination of nettypes and netids.
88 Whatever the value, it is first treated as a net‐
89 type. If it is not a valid nettype, then it is
90 treated as a netid. For example, rpc/* for an RPC
91 service using all the transports supported by the
92 system (the list can be found in the /etc/netconfig
93 file), equivalent to saying rpc/visible rpc/ticots
94 for an RPC service using the Connection-Oriented
95 Transport Service.
96 wait-status This field has values wait or nowait. This entry
99 specifies whether the server that is invoked by
100 inetd will take over the listening socket associ‐
101 ated with the service, and whether once launched,
102 inetd will wait for that server to exit, if ever,
103 before it resumes listening for new service
104 requests. The wait-status for datagram servers must
105 be set to wait, as they are always invoked with the
106 orginal datagram socket that will participate in
107 delivering the service bound to the specified ser‐
108 vice. They do not have separate "listening" and
109 "accepting" sockets. Accordingly, do not configure
110 UDP services as nowait. This causes a race condi‐
111 tion by which the inetd program selects on the
112 socket and the server program reads from the
113 socket. Many server programs will be forked, and
114 performance will be severely compromised. Connec‐
115 tion-oriented services such as TCP stream services
116 can be designed to be either wait or nowait status.
117 uid The user ID under which the server should run. This
120 allows servers to run with access privileges other
121 than those for root.
122 server-program Either the pathname of a server program to be
125 invoked by inetd to perform the requested service,
126 or the value internal if inetd itself provides the
127 service.
128 server-arguments If a server must be invoked with command line argu‐
131 ments, the entire command line (including argument
132 0) must appear in this field (which consists of all
133 remaining words in the entry). If the server
134 expects inetd to pass it the address of its peer,
135 for compatibility with 4.2BSD executable daemons,
136 then the first argument to the command should be
137 specified as %A. No more than 20 arguments are
138 allowed in this field. The %A argument is imple‐
139 mented only for services whose wait-status value is
140 nowait.
141
144 /etc/netconfig network configuration file
145 /etc/inet/protocols Internet protocols
148 /etc/inet/services Internet network services
151
154 rlogin(1), rsh(1), in.tftpd(1M), inetadm(1M), inetconv(1M), inetd(1M),
155 services(4), smf(5)
156
158 /etc/inet/inetd.conf is the official SVR4 name of the inetd.conf file.
159 The symbolic link /etc/inetd.conf exists for BSD compatibility.
160 This man page describes inetd.conf as it was supported in Solaris oper‐
163 ating system releases prior to the current release. The services that
164 were configured by means of inetd.conf are now configured in the Ser‐
165 vice Management Facility (see smf(5)) using inetadm(1M).
166SunOS 5.11 17 Dec 2004 inetd.conf(4)