Software /
code /
prosody-modules
File
mod_debug_traceback/README.markdown @ 5366:db4c66a1d24b
mod_http_oauth2: Fill in some client metadata defaults
Explicit > Implicit
Maybe we should actually use these for something as well? :)
It's is somewhat an open question of how strictly we should enforce
things in the client metadata given that it is somewhat extensible.
Especially some of these enum fields which have corresponding IANA
registries.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Tue, 25 Apr 2023 18:09:08 +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.