Mercurial > p > roundup > code
view doc/debugging.txt @ 3911:daedf66344f7
add an example to roundup-server's man page
I also made a slight change to the name=tracker_instance
portion to hopefully clarify that "name" is a variable.
hopefully this will eliminate some of the confusion in
[SF#1637358]
Suggestions about better clarifications are welcome :)
| author | Justus Pendleton <jpend@users.sourceforge.net> |
|---|---|
| date | Thu, 20 Sep 2007 17:03:17 +0000 |
| parents | 94e430ad4fdb |
| children | b6f1aaba4827 |
line wrap: on
line source
Debugging Flags --------------- Roundup uses a number of debugging environment variables to help you figure out what the heck it's doing. HYPERDBDEBUG ============ This environment variable should be set to a filename - the hyperdb will write debugging information for various events (including, for instance, the SQL used). This is only obeyed when python is _not_ running in -O mode. HYPERDBTRACE ============ This environment variable should be set to a filename - the hyperdb will write a timestamp entry for various events. This appears to be suffering rather extreme bit-rot and may go away soon. This is only obeyed when python is _not_ running in -O mode. SENDMAILDEBUG ============= Set to a filename and roundup will write a copy of each email message that it sends to that file. This environment variable is independent of the python -O flag.
