Open System Services Management and Operations Guide (G06.25+, H06.03+)

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-30
Configuring Network Services Servers, Tools, and
Applications
portmap
The portmap process is configured either by creating NonStop operating system
DEFINEs for it in the TACL session used to start it or by passing parameter values to it
in the command that starts it.
You can change the following by specifying an ADD DEFINE command at a TACL
prompt before starting portmap:
•
The TCP/IP (transport-provider) process used by portmap. For example:
ADD DEFINE =TCPIP^PROCESS^NAME, FILE $ZTC1
•
The TCP/IP domain name resolution (resolver configuration) file used by portmap.
For example:
ADD DEFINE =TCPIP^RESOLVER^NAME, FILE ALTRES
•
The TCP/IP host definition file used by portmap. For example:
ADD DEFINE =TCPIP^HOST^FILE, FILE ALTHOST
Some declarations are not valid in certain combinations. See the portmap(8)
reference page either online or in the Open System Services Shell and Utilities
Reference Manual for more information about the command to start portmap and the
configuration information that can be specified for it.
rshd
You configure the rshd process by:
1. Adding the following entry to the configuration file used for the inetd process:
shell stream tcp nowait root /bin/rshd
2. Stopping and restarting inetd. Alternatively, you can force inetd to reread its
configuration file, as described in the inetd(8) reference page either online or in
the Open System Services Shell and Utilities Reference Manual.
You must also configure the OSS environment for users of the rsh command on
workstations or other NonStop servers. Each rsh user must have either a NonStop
operating system user ID and login name or an alias configured through Safeguard. If
an alias is used, the user must also have an initial working directory (specified by the
Safeguard INITIAL-DIRECTORY attribute) defined for it in the OSS file system.
You can also set up an /etc/hosts.equiv file or .rhosts files for remote rsh
command users.
Caution. These files can be used by intruders to compromise your system’s security. Create
and secure them carefully. The /etc/hosts.equiv file must be owned by the super ID and
only the super ID must have writer permission for it. An .rhosts file must be owned by the
NonStop operating system user ID or alias that owns the initial working directory in which it
resides and it must be secured such that only the owner has write permission for it.