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

Managing Servers
Open System Services Management and Operations Guide—527191-005
4-31
Configuring the OSS Transport Agent Servers
°
To reassign the process to a new primary or backup processor, change the
corresponding processor entry.
°
To change behavior associated with use of the automatic startup service,
change the corresponding BACKUPCPUOK, MAXWAITTIME,
DESIREDSTATE, or AUTORESTART entry.
3. To restart the server, enter this OSS Monitor SCF command:
START SERVER $ZPMON.#ZPLS
If you use the STARTOSS utility at your site, you can also configure the OSS sockets
local server to be started by that utility. To do so, add the server name to the OSSINFIL
file. See OSSINFIL File on page C-19 for more information.
Configuring the OSS Transport Agent Servers
You cannot configure an OSS transport agent server. The OSS Monitor SCF ALTER
SERVER command is not valid for OSS transport agent servers.
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 Network Services Servers, Tools, and Applications
The following subsections briefly discuss configuring:
•
inetd on page 4-31
•
portmap on page 4-32
•
rshd on page 4-33
•
rexecd on page 4-34
•
OSS Sockets Applications on page 4-34
The RPCINFO program is configured using an EDIT file in the Guardian environment;
see Configuration Files for the Network Services Servers and Tools on page 4-24 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