[About] [News] [Documentation] [Screenshots]
Name
bugle-log — configure logging output from other filter-sets
Synopsis
filterset log
{
filename "bugle.log"
file_level "4"
stdout_level "0"
stderr_level "3"
flush "no"
format "[%l] %f.%e: %m"
}Description
The log filter-set does not do any logging itself; instead, it provides logging services to other filter-sets. It is always loaded, but it may be explicitly listed in the configuration file to set options. The log is always written to standard error, but it can be written to file as well. It is also possible to control the log level.
Options
filenameThis sets the file for logging. Logging is still done to standard error. Note that with the default settings, the file log is more verbose than the standard error log.
file_levelThe log level for the log file, where a higher number means more verbose logging. The levels are:
- 0
No logging at all
- 1
Errors, usually leading to immediate termination
- 2
Warnings, usually affecting bugle's functionality
- 3
Notices, usually OpenGL errors or undefined behaviour
- 4
Info from filtersets that generate logs, such as bugle-trace(7)
- 5
Debugging messages
stdout_level,stderr_levelSimilar to
file_level, but for logging to standard output and standard error. The defaults are 4 for a file, 0 (no logging) for standard out, and 3 for standard error.formatOverrides the default log format. The following printf-style escapes are recognised:
%llog level
%ffilter-set
%eevent
%mthe log message itself
%pprocess ID
%tthread ID
%%a literal
%