TCP/IP Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

111

112

113

114

115

116

117

118

119

120

Configuring the NonStop TCP/IP Subsystem

TCP/IP Configuration and Management Manual—427132-004

3-59

Installing inetd

Starting inetd

To start inetd, enter the following command at the shell prompt:

If inetd is already running, you need to kill the first one before starting a new one. First,

get the OSS process identification (OSS PID) of the running inetd daemon by using the

ps command. Then, enter one of the following commands:

Upon starting, inetd reads in the inetd.conf file, located in the /etc directory.

Preventing Port Collisions

Collisions between the services provided by the Guardian LISTNER process and the

inetd daemon can occur if the LISTNER process in the Guardian environment and the

inetd daemon in the OSS environment are assigned to the same TCP/IP process using

the same port and protocol.

In the above case, the inetd daemon does not connect for a specific service,

and an EMS event is generated. The inetd daemon retries the connection; EMS

events accompany all subsequent rejections. To check for this condition, use the

event viewer provided by TSM (G-series RVUs only). To prevent this condition,

specify a TCP/IP process (Transport Provider) that doesn’t have LISTNER

running on it by using the command shown in Example 3-21

or modify the

configuration files to prevent port collisions as described below.

Modify the Configuration Files to Prevent Port Collisions

As an alternative to specifying a TCP/IP process other than the default, (and one that

doesn’t have a LISTNER process), you can modify either one or both of the

configuration files (portconf and inetd.conf). First, determine which services between

the Guardian LISTNER process and the OSS inetd process conflict by looking at the

portconf and inetd.conf files). Then, make one of the following modifications:



Disable the conflicting services in the Guardian LISTNER’s portconf file (by

commenting them out). In this case, the inetd daemon provides the service.



Disable the conflicting services in the OSS inetd’s inetd.conf file (by commenting

them out). In this case, the LISTNER provides the service.

<shell prompt> /usr/ucb/inetd

Note. The inetd sockets application specifies a check for an environment variable to determine

which TCP/IP process (Transport Provider) to use.