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

If processors are added to your node or brought up after the OSS Monitor starts, the OSS Monitor
configuration database will not contain entries for the OSS transport-agent servers in those
processors. To force the OSS Monitor to update its database and add entries for those servers,
you must stop and restart the OSS Monitor.
Configuring the OSS Resource Agent Servers
You cannot configure an OSS resource agent server. The OSS Monitor SCF ALTER SERVER command
is not valid for OSS resource agent servers.
Configuring Network Services Servers, Tools, and Applications
The following subsections briefly discuss configuring:
• “inetd” (page 123)
• “portmap” (page 124)
• “rshd” (page 124)
• “rexecd” (page 125)
• “OSS Sockets Applications” (page 125)
The RPCINFO program is configured using an EDIT file in the Guardian environment; see
“Configuration Files for the Network Services Servers and Tools” (page 117) for more information.
Information about configuring the BIND 9 domain name server named and the lightweight resolver
server can be found in the DNS Configuration and Management Manual and the lwresd(8),
dnssec_ named(8), named(8), dnssec_nsupdate(8), nsupdate(8), dnssec_rndc(8),
and rndc(8) reference pages online.
inetd
To prevent confusion and conflicts between servers, you should use and maintain the Guardian
version of the inetd configuration files for both environments when Guardian versions exist. The
Guardian files can be set up for use from the OSS environment by creating symbolic links between
the Guardian files and the /etc directory:
1. Check that the files or links do not already exist in the /etc directory by entering the following
command at an OSS shell prompt:
cd /etc
ls -al
If resolv.conf, hosts, and inetd.conf appear, ignore the rest of this procedure and
see “portmap” (page 124) to configure the portmap process.
NOTE: inetd can use any configuration file identified to it during its startup. The default
configuration file is /etc/inetd.conf. If you use the /etc/inetd.conf file and your
system does not initially have a smplinetd.conf file, your entries in /etc/inetd.conf
can be overwritten during a product update; you should make a backup of the configuration
file whenever you change that file. You can make a backup by entering the following at an
OSS shell prompt:
cp /etc/inetd.conf /etc/inetd.conf.bak
2. If inetd.conf does not appear but smplnetd.conf appears, at the OSS shell prompt,
enter:
cp smplinetd.conf inetd.conf
However, see the note above; in this guide, the filename is presumed to be inetd.conf,
but your site might use alternative names.
3. If neither inetd.conf or smplnetd.conf appears, at the OSS shell prompt, enter:
ln -s /G/system/ztcpip/inetconf inetd.conf
Configuration Files 123