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

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-31
Configuring Network Services Servers, Tools, and
Applications
See the .rhosts(4) and hosts.equiv(4) reference pages either online or in the
Open System Services Shell and Utilities Reference Manual for more information
about these files.
See the rshd(8) reference page either online or in the Open System Services Shell
and Utilities Reference Manual for information about setting up the rshd process. See
Section 8, Managing Security, for more information about setting up aliases and initial
working directories.
rexecd
To configure the rexecd process:
1. Ensure that the /etc/services file is accessible by entering:
cd /etc
ls -al
If the /etc/services file is not listed, follow the directions in Configuring
Network Services on page 4-32 to make it accessible, then continue with Step 2.
2. Add a port specification for the exec service to the /etc/services file.
3. Add the following entry to the configuration file used for the inetd process:
exec stream tcp nowait super.super /bin/rexecd
4. Stop and restart 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 remote users of the rexecd server.
Each user of the rexecd server 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.
See the rexecd(8) reference page either online or in the Open System Services
Shell and Utilities Reference Manual for more information about the rexecd process.
OSS Sockets Applications
If your site runs applications that use OSS sockets:
•
You should confirm the existence of a $ZTC0 TCP/IP process or define a substitute
for that process. Unless an AF_INET or AF_INET6 sockets application program is
coded to select its own transport-provider process, it attempts to use the $ZTC0
default process and fails if there is no $ZTC0 transport-provider process; defining a
substitute for the default avoids this situation.
•
You must configure network services that such applications might use.