Developer Store
Support
Member Forums

Screenshots
FAQ
Documentation
License
Known Issues
Downloads

MMOWorkshop BACK!

PyTorque
TGB Web Browser


grogbro

hallsofvalhalla - Been A while
xapken - Wizards and Champions
J.C. Smith - The Repopulation - 0.5.2 Build Notes
EmpireGames - Elementals in Rise of Heroes
Empire Games - WarPath.
jaidurn - Warcall 0.0.1.0 build notes
medafor - Final detailing of models
Thamior - Presence system GONE! [May 25th 2009)]
... MORE BLOGS!

Building a MMO
Wow I had no idea....
Quest Remnants of Chaos
Checking to see if anyone is sti...
Well here I am again :)
T3D and MMOKit
afx 2.0
Terrain specularity [video]
Torque T3D MMO Kit
[3dFoin] Dragon Bug

Trac Logging

Trac supports logging of system messages using the standard logging module that comes with Python.

Logging is configured in the [logging] section in trac.ini.

Supported Logging Methods

The log method is set using the log_type configuration option, which takes any of the following values:

none
Suppress all log messages.
file
Log messages to a file, specified with the log_file option in trac.ini.
stderr
Output all log entries to console (tracd only).
syslog
(UNIX) Send messages to local syslogd via named pipe /dev/log.
eventlog
(Windows) Use the system's NT eventlog for Trac logging.

Log Levels

The verbosity level of logged messages can be set using the log_level directive in trac.ini. The log level defines the minimum level of urgency required for a message to be logged.

The levels are:

CRITICAL
Log only the most critical (typically fatal) errors.
ERROR
Log failures, bugs and errors.
WARN
Log warnings, non-interrupting events.
INFO
Diagnostic information, log information about all processing.
DEBUG
Trace messages, profiling, etc.


See also: TracIni, TracGuide, TracEnvironment