Page 657

protocol	Determines the protocol that is employed by the service. The protocol must exist in /etc/protocols. If this attribute is not defined, the default protocol employed by the service will be used.
wait	This attribute determines if the service is single-threaded or multithreaded. If its value is yes, the service is single-threaded; this means that xinetd will start the server and then it will stop handling requests for the service until the server dies. If the attribute value is no, the service is multithreaded and xinetd will keep handling new service requests.
user	Determines the uid for the server process. The username must exist in /etc/passwd. This attribute is ineffective if the xinetd effective user ID of xinetd is not super-user.
group	Determines the gid for the server process. The group name must exist in /etc/group. If a group is not specified, the group of user will be used (from /etc/passwd). This attribute is ineffective if the effective user ID of xinetd is not super-user.
instances	Determines the number of servers that can be simultaneously active for a service. By default, there is no limit. The value of this attribute can be either a number or UNLIMITED, which means that there is no limit.
server	Determines the program to execute for this service.
server_args	Determines the arguments passed to the server. In contrast to inetd, the server name should not be included in server_args.
only_from	Determines the remote hosts to which the particular service is available. Its value is a list of IP addresses that can be specified in any combination of the following ways:
	a) A numeric address in the form of %d.%d.%d.%d. If the rightmost components are 0, they are treated as wildcards (for example, 128.138.12.0 matches all hosts on the 128.138.12 subnet). 0.0.0.0 matches all Internet addresses.
	b) A factorized address in the form of %d.%d.%d.{%d,%d,...}. There is no need for all four components (%d.%d.{%d,%d,...%d} is also OK). However, the factorized part must be at the end of the address.
	c) A network name (from /etc/networks).
	d) A hostname. All IP addresses of the specified hostname will be used.
""	Specifying this attribute without a value makes the service available to nobody.
no_access	Determines the remote hosts to which the particular service is unavailable. Its value can be specified in the same way as the value of the only from attribute. These two attributes determine the location access control enforced by xinetd. If none of the two is specified for a service, the service is available to anyone. If both are specified for a service, the one that is the better match for the address of the remote host determines if the service is available to that host (for example, if the only from list contains 128.138.209.0 and the no access list contains 128.138.209.10, then the host with the address 128.138.209.10 can not access the service).

Page 658

access_times Determines the time intervals when the service is available. An interval has the form hour:min-hour:min (connections will be accepted at the bounds of an interval). Hours can range from 0 to 23 and minutes from 0 to 59. log_type Determines where the service log output is sent. There are two formats:

	SYSLOG syslog	The log output is sent to syslog at
	facility	the specified facility. If a level
	[syslog level]	is present, the messages will be recorded at that level instead of LOG_INFO (which is the default level).
	FILE file	The log output is appended to file,
	[soft_limit	which will be created if it does
	[hard_limit]]	not exist. Two limits on the size of the log file can be optionally specified. The first limit is a soft one; xinetd will log a message the first time this limit is exceeded (if xinetd logs to syslog, the message will be sent at the LOG_ALERT priority level). The second limit is a hard limit; xinetd will stop logging for the affected service (if the log file is a common log file, then more than one service may be affected) and will log a message about this (if xinetd logs to syslog, the message will be sent at the LOG_ALERT priority level). If a hard limit is not specified, itdefaults to the soft limit increased by 1 percent but the extra size must be within the parameters LOG_EXTRA_MIN and LOG_EXTRA_MAX (defined in config.h).

log_on_success

Determines what information is logged when a server is started and when that server exits (the service ID is always included in the log entry). Any combination of the following values may be specified:

	PID	Logs the server process ID. (If the service is implemented by xinetd without forking another process, the logged process ID will be 0.)
	HOST	Logs the remote host address
	TIME	Logs the time when the server was started.
	USERID	Logs the user ID of the remote user using the RFC 931 identification protocol. This option is available only for multithreaded stream services.
	EXIT	Logs the fact that a server exited along with the exit status or the termination signal (the process ID is also logged if the PID option is used).
	DURATION	Logs the duration of a service session.

log_on_failure

Determines what information is logged when a server cannot be started (either because of a lack of resources or because of access control restrictions). The service ID is always included in the log entry along with the reason for failure. Any combination of the following values may be specified:

HOST

Logs the remote host address.

Previous | Table of Contents | Next