16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

inetd daemon<br />

Usage notes<br />

1. Buffer sizes should only be specified if the documentation for the daemon being<br />

specified in the inetd.conf statement calls for something other than the default.<br />

2. The configuration file is field-sensitive, but not column-sensitive. Fields should<br />

be arranged in the order shown in Table 13. Continuation lines for an entry must<br />

begin with a space or tab. Each entry must contain all fields. The inetd daemon<br />

uses the configuration file entry to properly set up the environment expected by<br />

the server. Specifying an incorrect value for one or more of the parameters is<br />

likely to cause the server to fail.<br />

Table 13. Fields in the Configuration File (inetd daemon)<br />

[ip_address:]service_name ip_address is a local IP, followed by a colon. If specified, the address is used<br />

instead of INADDR_ANY or the current default. To specifically request<br />

INADDR_ANY, use ″*:″. If ip_address (or a colon) is specified, without any<br />

other entries on the line, it becomes the default for subsequent lines until a<br />

new default is specified. service_name is a well-known service name such<br />

as login or shell. The name and protocol specified must match one of the<br />

server names defined in /etc/services. For more information on<br />

/etc/services, see z/<strong>OS</strong> Communications Server: IP Configuration<br />

Reference. and z/<strong>OS</strong> Communications Server: New Function Summary<br />

socket_type Stream or dgram<br />

protocol[,sndbuf=n][,rcvbuf=n] protocol can be tcp or udp, or (for IPv6) tcp6 or udp6. tcp4 and udp4 can<br />

also be specified to explicitly request IPv4. The protocol is used to further<br />

qualify the service name. Both the service name and the protocol should<br />

match an entry in /etc/services, except that, the ″4″ or the ″6″ should not<br />

be included in the /etc/services entry. For more information on<br />

/etc/services, see z/<strong>OS</strong> Communications Server: IP Configuration<br />

Reference and z/<strong>OS</strong> Communications Server: New Function Summary. Note<br />

that, if tcp6 or udp6 is specified, the socket will support IPv6 (that is,<br />

AF_INET6 will be used.)<br />

sndbuf and rcvbuf specify the size of the send and receive buffers. The size<br />

may be in bytes, or a ″k″ or ″m″ may be added to indicate kilobytes or<br />

megabytes respectively. sndbug and rcvbuf can be used in either order.<br />

wait_flag [.max] Wait or nowait. Wait indicates the daemon is single-threaded and another<br />

request will not be serviced until the first one completes.<br />

314 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference<br />

If nowait is specified, the inet daemon issues an accept when a connect<br />

request is received on a stream socket. If wait is specified, the inet daemon<br />

does not issue the accept. It is the responsibility of the server to issue the<br />

accept if this is a stream socket.<br />

max is the maximum number of users allowed to request service in a 60<br />

second interval. Default is 40. If exceeded, the service’s port is shut down.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!