Open System Services Management and Operations Guide (G06.30+, H06.08+, J06.03+)

There are two versions of the resolver that you can use on a node. Each version has its own rules
for the content of its resolver configuration file:
• The BIND 4 version is described in the resolv.conf(4) reference page online and in the
Open System Services Shell and Utilities Reference Manual
• The BIND 9 version is described in the resolv.conf(5) reference page online and in the
Open System Services Shell and Utilities Reference Manual
The Guardian resolver configuration file can be changed from $SYSTEM.ZTCPIP.RESCONF by
using the DEFINE =TCPIP^RESOLVER^NAME. The equivalent ability for the OSS environment is
provided by using the OSS shell export command or the putenv() function to set the
TCPIP_RESOLVER_NAME environment variable to a value other than /etc/resolv.conf.
HP provides a default version of each of these files. See the TCP/IP Configuration and Management
Manual or the TCP/IPv6 Configuration and Management Manual for more information about these
files; see “inetd” (page 123) and “OSS Sockets Applications” (page 125) for a description of how
to provide these files in the OSS environment.
Beginning with the J06.16 and H06.27 RVUs, the OSS Core Utilities product (T1202) provides
the extended Internet daemon, xinetd. This Open Source super-server daemon manages
Internet-based connectivity and offers a more secure extension to inetd. For more details, see
“OSS Core Utilities User Commands” (page 243).
rshd
The rshd process does not use a configuration file. However, the behavior of the rsh commands
that it services can be affected by the content of files on targeted systems:
• For a specific targeted UNIX system, see the rsh or rshd documentation of that system for
more information.
• For users of an rsh command on a remote UNIX system who want to gain access to the OSS
environment, you need to provide and properly secure the following configuration files in the
OSS file system:
◦ /etc/hosts.equiv
◦ .rhosts
The hosts.equiv file in the /etc directory of the OSS file system describes which hosts and
which users of each host are allowed to start remote shells on an OSS system. The .rhosts file
resides in the home directory within the OSS file system for each authorized remote user of the
OSS environment. The most important copy of .rhosts is the one that resides in the home directory
of the super ID because /etc/hosts.equiv is bypassed when a remote user attempts to use
an rsh command as the super ID.
These files are sometimes the target of UNIX system intruders. Take standard precautions for their
use on a UNIX system when setting them up for the OSS environment.
See the hosts.equiv(4) and .rhosts(4) reference pages either online or in the Open System
Services Shell and Utilities Reference Manual for more information about the content and use of
these files.
portmap
The portmap process uses the Guardian files configured for TCP/IP processes running in the
Guardian environment:
$SYSTEM.ZTCPIP.HOSTS $SYSTEM.ZTCPIP.RESCONF
HP provides a default version of each of these files. See the TCP/IP Configuration and Management
Manual or the TCP/IPv6 Configuration and Management Manual for more information about these
files. For information on changing the configuration of portmap, see “portmap” (page 124).
118 Managing Servers