Penguin
Recent Changes
Blame: inetd.conf(5)
EditPageHistoryDiffInfoLikePages
Annotated edit history of inetd.conf(5) version 3, including all changes. View license author blame.
Rev Author # Line
1 perry 1 ----
2 __NAME__
3
4
5 inetd.conf - Internet servers database
6 __DESCRIPTION__
7
8
9 Upon execution, inetd reads its configuration information
10 from a configuration file which, by default, is
11 /etc/inetd.conf. There must be an entry for each
12 field of the configuration file, with entries for each field
13 sepa- rated by a tab or a space. Comments are denoted by a
14 ``#'' at the beginning of a line. There must be an entry for
15 each field. The fields of the configuration file are as
16 follows:
17
18
19 service name
20 socket type
21 protocol
22 wait/nowait[[.max]
23 user[[.group]
24 server program
25 server program arguments
26 To specify an ''Sun-RPC'' based service, the entry would contain these fields.
27
28
29 service name/version
30 socket type
31 rpc/protocol
32 wait/nowait[[.max]
33 user[[.group]
34 server program
35 server program arguments
36 The ''service-name'' entry is the name of a valid service in the file /etc/services. For ``internal'' services (discussed below), the service name ''must'' be the official name of the service (that is, the first entry in /etc/services). When used to specify a ''Sun-RPC'' based service, this field is a valid RPC service name in the file /etc/rpc. The part on the right of the ``/'' is the RPC version number. This can simply be a single numeric argument or a range of versions. A range is bounded by the low version to the high version - ``rusers/1-3''.
37
38
39 The ''socket-type'' should be one of ``stream'',
40 ``dgram'', ``raw'', ``rdm'', or ``seqpacket'', depending on
41 whether the socket is a stream, datagram, raw, reliably
42 delivered mes- sage, or sequenced packet
43 socket.
44
45
46 The ''protocol'' must be a valid protocol as given in
47 /etc/protocols. Examples might be ``tcp'' or
48 ``udp''. Rpc based services are specified with the
49 ``rpc/tcp'' or ``rpc/udp'' service type.
50
51
52 The ''wait/nowait'' entry is applicable to datagram
53 sockets only (other sockets should have a ``nowait'' entry
54 in this space). If a datagram server connects to its peer,
55 freeing the socket so inetd can received further messages on
56 the socket, it is said to be a ``multi-threaded'' server,
57 and should use the ``nowait'' entry. For datagram servers
58 which process all incoming datagrams on a socket and
59 eventually time out, the server is said to be
60 ``single-threaded'' and should use a ``wait'' entry.
3 AristotlePagaltzis 61 comsat(8) (biff(1)) and talkd(8)
1 perry 62 are both examples of the latter type of datagram server.
3 AristotlePagaltzis 63 tftpd(8) is an exception; it is a datagram server
1 perry 64 that establishes pseudo-connections. It must be listed as
65 ``wait'' in order to avoid a race; the server reads the
66 first packet, creates a new socket, and then forks and exits
67 to allow inetd to check for new service requests to spawn
68 new servers. The optional ``max'' suffix (separated from
69 ``wait'' or ``nowait'' by a dot) specifies the maximum num-
70 ber of server instances that may be spawned from inetd
71 within an interval of 60 seconds. When omitted, ``max''
72 defaults to 40.
73
74
75 The ''user'' entry should contain the user name of the
76 user as whom the server should run. This allows for servers
77 to be given less permission than root. An optional group
78 name can be specified by appending a dot to the user name
79 followed by the group name. This allows for servers to run
80 with a dif- ferent (primary) group id than specified in the
81 password file. If a group is specified and user is not root,
82 the sup- plementary groups associated with that user will
83 still be set.
84
85
86 The ''server-program'' entry should contain the pathname
87 of the program which is to be executed by inetd when a
88 request is found on its socket. If inetd provides this
89 service inter- nally, this entry should be
90 ``internal''.
91
92
93 The ''server program arguments'' should be just as
94 arguments normally are, starting with argv[[0], which is the
95 name of the program. If the service is provided internally,
96 the word ``internal'' should take the place of this
97 entry.
98
99
100 Inetd provides several ``trivial'' services internally by
101 use of routines within itself. These services are ``echo'',
102 ``discard'', ``chargen'' (character generator), ``daytime''
103 (human readable time), and ``time'' (machine readable time,
104 in the form of the number of seconds since midnight, January
105 1, 1900). All of these services are tcp based. For details
106 of these services, consult the appropriate
107 RFC from the Net- work Information
108 Center.
109 __BUGS__
110
111
112 Lines in inetd.conf are limited to a maximum length of 1022
113 characters.
114 __SEE ALSO__
115
116
117 inetd(8)
118
119
2 perry 120 Linux !NetKit 0.10 November 23, 1996 1
1 perry 121 ----
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.