xinetd.log(5)

1XINETD.LOG(5)                 File Formats Manual                XINETD.LOG(5)
2
3
4

NAME

6       xinetd.log - xinetd service log format
7

DESCRIPTION

9       A  service  configuration  may  specify various degrees of logging when
10       attempts are made to access the service. When logging for a service  is
11       enabled,  xinetd will generate one-line log entries which have the fol‐
12       lowing format (all entries have a timestamp as a prefix):
13
14              entry: service-id data
15
16       The data depends on the entry.  Possible entry types include:
17
18              START       generated when a server is started
19
20              EXIT        generated when a server exits
21
22              FAIL        generated when it is not possible to start a server
23
24              USERID      generated if the USERID log option is used.
25
26              NOID        generated if the USERID log option is used, and  the
27                          IDONLY service flag is used, and the remote end does
28                          not identify who is trying to access the service.
29
30       In the following, the information enclosed in brackets appears  if  the
31       appropriate log option is used.
32
33       A START entry has the format:
34
35              START: service-id [pid=%d] [from=%d.%d.%d.%d]
36
37       An EXIT entry has the format:
38
39              EXIT: service-id [type=%d] [pid=%d] [duration=%d(sec)]
40
41       type  can  be  either  status or signal.  The number is either the exit
42       status or the signal that caused process termination.
43
44       A FAIL entry has the format:
45
46              FAIL: service-id reason [from=%d.%d.%d.%d]
47
48       Possible reasons are:
49
50              fork           a certain number  of  consecutive  fork  attempts
51                             failed (this number is a configurable parameter)
52
53              time           the time check failed
54
55              address        the address check failed
56
57              service_limit  the  allowed  number of server instances for this
58                             service would be exceeded
59
60              process_limit  a limit on the number  of  forked  processes  was
61                             specified and it would be exceeded
62
63       A DATA entry has the format:
64
65              DATA: service-id data
66
67       The data logged depends on the service.
68
69              login       remote_user=%s local_user=%s tty=%s
70
71              exec        remote_user=%s verify=status command=%s
72                          Possible status values:
73
74                          ok        the password was correct
75
76                          failed    the password was incorrect
77
78                          baduser   no such user
79
80              shell       remote_user=%s local_user=%s command=%s
81
82              finger      received string or EMPTY-LINE
83
84       A USERID entry has the format:
85
86              USERID: service-id text
87
88       The text is the response of the identification daemon at the remote end
89       excluding the port numbers (which are included in the response).
90
91       A NOID entry has the format:
92
93              NOID: service-id IP-address reason
94

NAME

DESCRIPTION

SEE ALSO