Log tags
--------

Zorp messages are separated into some container.
Every proxy has it's owns, and there are some container in core.

The containers, for now:

core
plug
ftp
http

Every container has subcontainers.

Core subcontainers:

session    -- Messages about sessions. (Chainers, data flows, etc.)
connect    -- Messages about connections. (Who conect to zorp, where zorp
              connect, connect was succesfull?)
proxy      -- Messages about proxy-s. (Proxy instance starting.)
policy     -- Messages about polices. (DAC, MAC violation, checks.)

Every proxy must have this predefined subcontainer:

connect    -- Connection to and from proxy.
request    -- data going to server. (from client or proxy)
answer     -- data going to client. (fom server or proxy)
debug      -- debug informations about proxy working.
accounting -- Accounting informations. (How long the proxy run, how many
              bytes go to server and client, etc.)

Proxies may have another subcontainers, but the above ones must handle
equaly.

Verbosity levels:
------------------

In every container in 0 level, no logging happens.

See, what's will logged, in various containers. In every logging levels
write the appropriate messages, and all messages adequate logging levels
below the topical logging level.

  connect
    0 - nothing
    1 - succesfull connections to proxy
    2 - succesfull connections from proxy
    3 - connection trying from client
    4 - connection trying to server
  session
    0 - nothing
    1 - session start-stop
    2 - started chainer
    3 - Sending and receiving IP number and port about this session
  policy
    0 - nothing
    1 - policy violation, policy errors.
    6 - policy testing
    7 - policy informations in testing (subjects nad objects MAC labels)

  request
    0 - nothing
    3 - dropped request
    6 - changed request
    7 - incoming request
  reply
    0 - nothing
    3 - dropped answer
    6 - changed answer
    7 - incoming answer
  accounting
    0 - nothing
    4 - username (if possible)
    5 - full traffic (in bytes)
    5 - outgoing (server side) traffic (in bytes)
    5 - incoming (client side) traffic (in bytes)
    5 - time, the proxy was ran.
    6 - other accounting informations.
  debug
    0 - nothing
    5 - important informations.
    6 - running informations. (may interested system administrators)
    7 - running informations. (function calling, etc. It's imoprtant when
        searching bugs)
    8 - Every useful informations about bug tracking. (Must be enabled with
        a compiled option.)
  error
    0 - problems, blocking zorp
    1 - problems, blocking proxy
    2 - problems, blocking request
    4 - minor problems. (doesn't block anything, in user's side)
