|
Previous | Table of Contents | Next
Page 659
|
|
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.
| |
|
ATTEMPT
|
Logs the fact that a failed attempt was made.
| |
|
RECORD
|
Records information from the remote end in
case the server could not be started. This allows monitoring of attempts to use the service.
For example, the login service logs the local
user, remote user, and terminal type. Currently,
the services that support this option are logiun,
shell, exec, finger.
|
|
rpc_version
|
Determines the RPC version for an RPC service.
The version can be a single number or a range in the
form number-number.
| |
env
|
The value of this attribute is a list of strings of the
form name=value. These strings will be added to the
environment before starting a server (therefore the server's
environment will include xinetd's environment plus the specified strings).
| |
passenv
|
The value of this attribute is a list of environment
variables from xinetd's environment that will be passed to the server.
| |
port
|
Determines the service port. If this attribute is specified
for a service listed in /etc/services, it must be equal to the
port number listed in that file.
|
You don't need to specify all of the preceding attributes for each service. The necessary attributes for a service are
the following:
|
socket type
|
| |
user
|
(non-unlisted services only)
| |
server
|
(non-internal services only)
| |
wait
|
| |
protocol
|
(RPC and unlisted services only)
| |
rpc_version
|
(RPC services only)
| |
port
|
(unlisted services only)
|
The following attributes support all assignment operators, except as indicated:
|
only_from
|
| |
no_access
|
| |
log_on_success
|
| |
log_on_failure
|
| |
passenv
|
| |
env
|
(does not support the -= operator)
|
These attributes can also appear more than once in a service entry. The remaining attributes support only the
= operator and can appear at most once in a service entry.
The configuration file may also contain a single defaults entry that has the form:
defaults
{
<attribute> = <value><value> ...
...
}
Page 660
This entry provides default attribute values for service entries that don't specify those attributes. Possible
default attributes:
< /P>
|
log_type
|
| |
log_on_success
|
(cumulative effect)
| |
log_on_failure
|
(cumulative effect)
|
Previous | Table of Contents | Next
|
