prosody-modules
460f78654864
mod_debug_traceback/README.markdown
Software / code / prosody-modules
File
mod_debug_traceback/README.markdown @ 5173:460f78654864
mod_muc_rtbl: also filter messages
This was a bit tricky because we don't want to run the JIDs
through SHA256 on each message. Took a while to come up with this
simple plan of just caching the SHA256 of the JIDs on the
occupants.
This will leave some dirt in the occupants after unloading the
module, but that should be ok; once they cycle the room, the
hashes will be gone.
This is direly needed, otherwise, there is a tight race between
the moderation activities and the actors joining the room.
| author | Jonas Schäfer <jonas@wielicki.name> |
|---|---|
| date | Tue, 21 Feb 2023 21:37:27 +0100 |
| 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.
