table of contents
| XINETD.LOG(5) | File Formats Manual | XINETD.LOG(5) |
NAME¶
xinetd.log - xinetd service log format
DESCRIPTION¶
A service configuration may specify various degrees of logging when attempts are made to access the service. When logging for a service is enabled, xinetd will generate one-line log entries which have the following format (all entries have a timestamp as a prefix):
The data depends on the entry. Possible entry types include:
- START
- generated when a server is started
- EXIT
- generated when a server exits
- FAIL
- generated when it is not possible to start a server
- USERID
- generated if the USERID log option is used.
- NOID
- generated if the USERID log option is used, and the IDONLY service flag is used, and the remote end does not identify who is trying to access the service.
In the following, the information enclosed in brackets appears if the appropriate log option is used.
A START entry has the format:
An EXIT entry has the format:
type can be either status or signal. The number is either the exit status or the signal that caused process termination.
A FAIL entry has the format:
Possible reasons are:
- fork
- a certain number of consecutive fork attempts failed (this number is a configurable parameter)
- time
- the time check failed
- address
- the address check failed
- service_limit
- the allowed number of server instances for this service would be exceeded
- process_limit
- a limit on the number of forked processes was specified and it would be exceeded
A DATA entry has the format:
The data logged depends on the service.
A USERID entry has the format:
The text is the response of the identification daemon at the remote end excluding the port numbers (which are included in the response).
A NOID entry has the format:
SEE ALSO¶
xinetd(1L), xinetd.conf(5)
| 28 April 1993 |