inetd.conf(4M) DG/UX R4.11MU05 inetd.conf(4M)
NAME
inetd.conf - Internet servers database
DESCRIPTION
The inetd.conf file contains the list of servers that inetd(1M)
invokes when it receives an Internet request over a socket. Each
server entry is composed of a single line of the form:
service-name socket-type protocol wait-status uid server-program
server-args
You can separate fields with spaces or TAB characters. A `#' (pound-
sign) indicates the beginning of a comment; characters up to the end
of the line are not interpreted by routines that search this file.
service-name is the name of a valid service listed in the file
/etc/services. For RPC services, the value of
the service-name field consists of the RPC
service name, followed by a slash and either a
version number or a range of version numbers.
socket-type can be one of:
stream for a stream socket,
dgram for a datagram socket,
raw for a raw socket,
tli for a Transport Layer Interface (TLI)
endpoint.
protocol must be a recognized protocol listed in the file
/etc/protocols. For RPC services, the field
consists of the string "rpc" followed by a slash
and the name of the protocol (for example,
rpc/udp for an RPC service using the UDP protocol
as a transport mechanism).
For type tli endpoints, this field represents the
source provider. If the source provider does not
begin with /, it is assumed to be in /dev.
wait-status is nowait for all but "single-threaded" datagram
servers -- servers which do not release the
socket until a timeout occurs. These must have
the status wait.
uid[:net][:trusted] is the user ID under which the server should run.
This allows servers to run with access privileges
other than those for root. The user ID can be
optionally followed by a colon-separated list of
keywords. These keywords only have an effect on
trusted DG/UX systems. The possible keywords
are: net and trusted.
The net keyword only has an effect on a system
running with network security (that is, Trusted
IP). If the net keyword is present, it tells
inetd to ignore the user ID specified in
/etc/inetd.conf and to use instead the user ID
supplied by Trusted IP for this session.
The trusted keyword only has an effect on a
trusted DG/UX system not running with CAC. If
the trusted keyword is present, inetd does not
communicate with the session monitor on behalf of
the service.
On a trusted DG/UX system running with CAC, inetd
communicates with the session monitor on behalf
of the service if the associated executable does
not have the DGCAPNETSESSIONINITIATOR
capability in its object permitted set.
Note that if inetd does communicate with the
session monitor on behalf of the service, this
implies that the user ID (from /etc/inetd.conf,
or from Trusted IP if the net keyword is
specified) must have service-name authorization
with no authentication required; otherwise, inetd
will deny the service request. See inetd(1M) for
more information.
server-program is either the pathname of a server program to be
invoked by inetd to perform the requested
service, or the value internal if inetd itself
provides the service.
server-args If a server must be invoked with command-line
arguments, the entire command line (including
argument 0) must appear in this field (which
consists of all remaining words in the entry).
If the server expects inetd to pass it the
address of its peer (for compatibility with
4.2BSD executable daemons), then the first
argument to the command should be specified as
`%A'.
On a trusted DG/UX system, inetd.conf is delivered with a number of
services deactivated. This prevents certain kinds of unauthorized
access to the system. To reactivate these services, edit
/etc/inetd.conf and send a hangup signal to inetd (dgkill -1 inetd)
to have it reread the file.
FILES
/etc/inetd.conf
/etc/services
/etc/protocols
SEE ALSO
inetd(1M), services(4).
Licensed material--property of copyright holder(s)