prosody-modules
c0cb43817b7c
mod_lastlog2/README.md
Software / code / prosody-modules
File
mod_lastlog2/README.md @ 6113:c0cb43817b7c
mod_compliance_latest: using module:log_status
diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua
--- a/mod_compliance_latest/mod_compliance_latest.lua
+++ b/mod_compliance_latest/mod_compliance_latest.lua
@@ -1,6 +1,6 @@
local success, err = pcall(function() module:depends("compliance_2023") end)
if not success then
- module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?")
- return 1, "Error: Couldn't load dependency mod_compliance_2023."
+module:log_status( "error", "Error, can't load module: mod_compliance_2023. Is this module downloaded into a folder readable by prosody?" )
+return false
end
| author | Menel <menel@snikket.de> |
|---|---|
| date | Mon, 23 Dec 2024 14:09:56 +0100 |
| parent | 6003:fe081789f7b5 |
| child | 6196:1447f076c970 |
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*
