Open System Services Management and Operations Guide (G06.29+, H06.07+)

Managing Servers
Open System Services Management and Operations Guide—527191-005
4-24
Configuration Files for the Network Services Servers
and Tools
Configuration Files for the Network Services Servers and Tools
The following subsections briefly discuss the configuration files for the following
programs:
•
inetd on page 4-24
•
rshd on page 4-25
•
portmap on page 4-26
•
RPCINFO on page 4-26
•
BIND 9 Domain Name Server and Tools on page 4-27
The remote execution server, rexecd, does not have a configuration file.
inetd
The inetd process reads its configuration file when it is started or interrupted. That file
defines the servers to be invoked when a request comes in from the network. The file
contains a table with port-to-service assignments, used to service requests that start
servers. Using the information in its configuration file, inetd invokes the appropriate
server for the connection request.
The configuration file used by inetd is either a default file or a file specified in the
command that starts inetd. The default configuration file is /etc/inetd.conf. HP
provides a default version of /etc/inetd.conf; see inetd on page 4-31 for a
description of how to modify /etc/inetd.conf. The $SYSTEM.ZTCPIP.PORTCONF
file provides analogous information for the Guardian LISTNER process, so you should
coordinate content between PORTCONF and the inetd configuration file.
See the inetd(8) reference page either online or in the Open System Services Shell
and Utilities Reference Manual for the format of entries in the inetd configuration file.
inetd and OSS sockets provide functions that depend on the content of the following
files in the /etc directory:
hosts
networks
protocols
resolv.conf
services
Caution. Changes to /etc/inetd.conf might be overwritten during any future installation
or reinstallation of the corresponding T9660 product files. See You configure the necessary
network services by making AF_INET or AF_INET6 sockets configuration files available in the
OSS file system. To prevent confusion and conflicts between servers, use and maintain the
Guardian version of the AF_INET or AF_INET6 sockets configuration files for both
environments. Set up the Guardian files for use from the OSS environment by creating
symbolic links between the Guardian files and the /etc directory. Check that the files or links do
not already exist in the /etc directory, then create them if necessary: on page 4-35 for ways to
avoid this problem.