From 0754bda285f17e6fb750ce6dea1db788e9e0ccde Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Mon, 18 Feb 2008 10:52:02 +0000 Subject: documented at least a bit about the debug settings --- doc/debug.html | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 doc/debug.html (limited to 'doc/debug.html') diff --git a/doc/debug.html b/doc/debug.html new file mode 100644 index 00000000..ad53d94f --- /dev/null +++ b/doc/debug.html @@ -0,0 +1,39 @@ + + +Debug Support + + + +

Debug Support

+Rsyslog provides a number of debug aids. Some of them are activated by +adding the --enable-rtinst ./configure option ("rtinst" means runtime +instrumentation). Turning debugging on obviously costs some performance +(in some cases considerable). +

This is document is just being created and thus terse.

Signals supported

SIGUSR1 - turns debug messages on and off (expect this signal +to go away over time)

SIGUSR2 - outputs debug information (including active threads +and a call stack) for the state when SIGUSR2 was received. This is a +one-time output. Can be sent as often as the user likes.

Environment Variables

Environment variables set several debug settings. This is +intended to become the primary way to configure debugging support. +Currently are defined:

RSYSLOG_DEBUGLOG="/path/to/debuglog/" - writes (allmost) +all debug message to the specified log file in addition to stdout. Some +system messages (e.g. segfault or abort message) are not written to the +file as we can not capture them.

[manual index] [rsyslog site]

+ \ No newline at end of file -- cgit v1.2.3