prosody-modules
b74d592df9e2
mod_debug_traceback/README.markdown
Software / code / prosody-modules
File
mod_debug_traceback/README.markdown @ 4989:b74d592df9e2
mod_http_muc_log: Remove dead code
This might be something left over since a different variant where the
loop went like `for n = i-1, i-100, -1 do ... end` i.e. it went trough a
fixed number of items instead of all the page until the current message.
Then it would have needed something to stop going over the end, but
since the checks are simple it shouldn't be much of a problem looping
over even a very busy day.
| author | Kim Alvefur <zash@zash.se> |
|---|---|
| date | Tue, 16 Aug 2022 01:27:59 +0200 |
| parent | 4214:5841d54cb6c6 |
| child | 5874:0358fcf14cd6 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: Generate tracebacks on-demand --- # Introduction This module writes out a traceback to a file when a chosen signal (by default `SIGUSR1`) is received. It can be useful to diagnose cases where Prosody is unresponsive. # Configuration `debug_traceback_filename` : The name of the file to write the traceback to. Some variables are supported, see [mod_log_ringbuffer] docs for more info. Defaults to `{paths.data}/traceback-{pid}-{count}.log`. `debug_traceback_signal` : The name of the signal to listen for. Defaults to `SIGUSR1`. # Compatibility Prosody 0.11 or later.
