NAME
xinetd.log - xinetd service log formatDESCRIPTION
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):
entry: service-id
data
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.
START: service-id [pid=%d]
[from=%d.%d.%d.%d]
An EXIT entry has the format:
EXIT: service-id [type=%d]
[pid=%d] [duration=%d(sec)]
FAIL: service-id reason
[from=%d.%d.%d.%d]
- 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
DATA: service-id data
- login
- remote_user=%s local_user=%s tty=%s
- exec
- remote_user=%s verify=status command=%s
- ok
- the password was correct
- failed
- the password was incorrect
- baduser
- no such user
- shell
- remote_user=%s local_user=%s command=%s
- finger
- received string or EMPTY-LINE
USERID: service-id text
NOID: service-id IP-address
reason
SEE ALSO
xinetd(1L), xinetd.conf(5)28 April 1993 |