IBM Hub/Switch Switch User Manual


 
Chapter 6 HPSS Configuration
350 September 2002 HPSS Installation Guide
Release 4.5, Revision 2
6.8.8.2.2 /etc/services, /etc/inetd.conf, and /etc/xinetd.d
To invoke the non-DCE/Encina part of the mover, the remote nodes’ inetd is utilized to start the
parent process when a connection is made to a port based on the Mover’s type specific
configuration (see section 6.8.8).
An entry must be added to the /etc/services file so that the inetd will be listening on the port to
which the Mover parent process (running on a DCE/Encina node) will connect. The port number
is one greater than that configured for the “TCP Listen Port” in the Mover’s type specific
configuration. For example, if the configure listen port is 5001, the following line must be added to
/etc/services:
hpss_mvr1 5002/tcp
For non-Linux systems
A corresponding entry must be added to the /etc/inetd.conf file, which will define which
executable to run and the arguments to use when a connection is detected. The sole argument
(other than the program name) is the pathname to a file that will contain an ASCII representation
of the configured encryption key for the Mover (see the next section for further details). For
example:
hpss_mvr1 stream tcp nowait root /opt/hpss/bin/hpss_mvr_tcp
hpss_mvr_tcp /var/hpss/etc/mvr_ek
Which will cause the executable /opt/hpss/bin/hpss_mvr_tcp to be run under the root user ID
when a connection is detected on port 5002. The Mover process will use the /var/hpss/etc/mvr_ek
file to read the encryption key that will be used to authenticate all connections made to this Mover.
After modifying the /etc/inetd.conf file, be sure to refresh the inetd daemon using the following
commands:
% ps -ef | grep inetd
root 6450 3154 0 Apr 29 - 0:02 /usr/sbin/inetd
hpss 17852 59370 2 16:50:25 pts/18 0:00 grep inetd
% kill -s USR2 6450
For Linux systems
A corresponding file must be added to the /etc/xinetd.d directory, which will define which
executable to run and the arguments to use when a connection is detected. The file will be given the
same name as the entry in /etc/services. Continuing the above example, a file called /etc/xinetd.d/
hpss_mvr1 would be created with the following contents:
service hpss_mvr1
{
disable = no
socket_type = stream
protocol = tcp
wait = yes