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

Managing Servers
Open System Services Management and Operations Guide—527191-002
4-29
Configuring Network Services Servers, Tools, and
Applications
•
rshd on page 4-30
•
rexecd on page 4-31
•
OSS Sockets Applications on page 4-31
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-23 for
more information.
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 on page 4-30 to configure the portmap process.
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
4. If one of the other files does not appear, create a symbolic link to its Guardian
equivalent by entering one or more of these commands at the OSS shell prompt:
ln -s /G/system/ztcpip/resconf resolv.conf (for TCP/IPv4 only)
ln -s /G/system/ztcpip/hosts hosts
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