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

Managing Servers
Open System Services Management and Operations Guide—527191-005
4-38
Starting an OSS Transport Agent Server
Starting an OSS Transport Agent Server
An OSS transport agent is started automatically when its processor starts. You do not
need to start an OSS transport agent server to use an OSS AF_UNIX, OSS AF_INET,
or OSS AF_INET6 sockets application in a given processor.
To restart a stopped OSS transport agent server:
1. Make sure that you are a member of the super group (255,nnn).
2. Enter an OSS Monitor SCF START SERVER Command. For example:
START SERVER $ZPMON.#ZTA15
Starting a Network Services Server
You start network services such as rshd and rexecd by starting the inetd process.
To start the inetd process, enter a command similar to the following from an OSS
shell prompt:
/usr/ucb/inetd -R 10 -W /G/INETD -L /etc/inetd.conf &
The maximum number of times a service can be invoked in one minute is controlled by
the -R flag to this command. The -W flag allows you to assign a process name to the
inetd process so that you can more easily identify and manage it using TACL
commands; in the example, the process is named $INETD.
If you start the inetd process using the -L flag, you can use a field within the
/etc/inetd.conf file to assign network service server processes to specific
processors or otherwise perform load-balancing for your node. You can also change
the file that inetd uses from /etc/inetd.conf to another file of your choice. See
the inetd(8) reference page either online or in the Open System Services Shell and
Utilities Reference Manual for a description of the format and flags for the inetd
command and a description of the fields within an inetd configuration file.
By default, inetd and all processes that it starts use $ZTC0 as their transport-provider
process. However, you can change that use. You make that change by doing either of
the following:
•
Specifying the PARAM SOCKET^TRANSPORT^NAME at a TACL prompt before
starting your OSS shell
•
Defining the OSS shell environment variable SOCKET_TRANSPORT_NAME before
starting inetd.
The ability to change transport-provider processes is useful when your node runs
several copies of its TCP/IP processes and you want to do load-balancing among
them. For example:
•
The following PARAM allows the $ZTC2 process to be used as the inetd
transport-provider process:
PARAM SOCKET^TRANSPORT^NAME $ZTC2