Mercurial > prosody-modules
view mod_lastlog2/README.markdown @ 5951:d6a695abb33c
mod_ping_muc: Delay ping a configurable amount of time
If a server is restarting, checking immediately before it has a chance
to complete its restart and get ready would often fail, preventing the
possibility of transparent restarts as supported by Prosody's mod_muc.
Reconnecting immediately when a connection is closed for being idle, or
because the remote server is trying to reclaim some resources, is also
counter-productive as the connection may fail.
Also, if there is some Internet routing problem affecting s2s, it may
help to wait a bit before checking, in case the problem resolved itself
in the mean time.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sun, 11 Aug 2024 16:10:24 +0200 |
parents | c5df6d53f17f |
children |
line wrap: on
line source
--- labels: - 'Stage-Beta' summary: Record last timestamp of events --- # Introduction Similar to [mod_lastlog], this module records the last timestamp of various events, but keeps the last timestamp per type of event, instead of the last event. # Usage As with all modules, copy it to your plugins directory and then add it to the modules\_enabled list: ``` {.lua} modules_enabled = { -- other modules "lastlog2", } ``` # Configuration There are some options you can add to your config file: Name Type Default Description ---------------------- --------- --------- --------------------------------- lastlog\_ip\_address boolean false Log the IP address of the user? # Usage You can check a user's last activity by running: prosodyctl mod_lastlog2 username@example.com # Compatibility Version State --------- ------- Any *TBD*