File: LOGS

package info (click to toggle)
prayer 1.3.5-dfsg1-2
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 6,396 kB
  • ctags: 3,309
  • sloc: ansic: 43,161; makefile: 810; sh: 451; perl: 166
file content (67 lines) | stat: -rw-r--r-- 2,601 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
$Cambridge: hermes/src/prayer/docs/LOGS,v 1.2 2008/09/16 09:59:56 dpc22 Exp $

There are normally four separate log files active in Prayer:

prayer:
  Miscellaneous logging for prayer frontend servers. Includes details of
  incoming connections and lots of informatation about SSL connections
  if verbose logging is switched on.

prayer_session:
  Miscellaneous logging for prayer-session backend servers. Includes
  details of incoming connections and lots of informatation about SSL
  connections if verbose logging is switched on and direct connection
  mode is enabled.

access_log:  Records each HTTP request made by a browser, with response code
session_log: Record session interactions
               - includes every command issued in verbose logging mode

access_log:
===========

Typical entry:

  Oct 28 20:04:30 [11433] [213.104.12.23] (443) GET / HTTP/1.0 -> 200 823 1.0
  ^                ^       ^               ^    ^
  |                |       |               |    +--- HTTP response line
  |                |       |               +-------- HTTP Port number
  |                |       +------------------------ IP address of peer
  |                +-------------------------------- Process ID (*)
  +------------------------------------------------- Date and Time

(*) Process ID may be [number:number] for session URLs, which indicates
    process ID of both the frontend and session processes involved.

Response part:

      -> 200 823 1.0
         ^   ^   ^
         |   |   +----- HTTP response type, typically 1.0 or 1.1
         |   +--------- Size if response in bytes
         +------------- HTTP response code

session_log:
============

Typical entries:

   Oct 23 17:35:21 [3373] (dpc22) [session_exchange] disp_delete
   Oct 23 17:35:21 [3373] (dpc22) [cmd_disp_delete]
      Deleted message number 3 from INBOX
   Oct 23 17:35:21 [3373] (dpc22) [session_redirect] display/4/45210

The first and third line only appear if verbose logging switched on: they
record the path of the program as new commands are dispatched.

  session_exchange() - represents a HTTP exchange with a client 
  session_redirect() - represenet an internal page substitution.

Typical format of lines in the session log:

   Oct 23 17:35:21 [3373] (dpc22) [cmd_disp_delete] Deleted message ...
   ^                ^      ^       ^
   |                |      |       +-- Function responsible for message
   |                |      +---------- Logged in user for this session
   |                +----------------- Process ID of login session
   +---------------------------------- Time and date