Mercurial > prosody-modules
view mod_persisthosts/mod_persisthosts.lua @ 5787:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
parents | 366fadb5c6e5 |
children |
line wrap: on
line source
-- mod_persisthosts module:set_global(); local set = require"util.set"; local stat = require"lfs".attributes; local resolve_relative_path = require"core.configmanager".resolve_relative_path; local vhost_path = module:get_option_string("persisthosts_path", "conf.d"); local path_pattern = resolve_relative_path(prosody.paths.config, vhost_path) .. "/%s.cfg.lua"; local original = set.new(); original:include(prosody.hosts); module:hook("host-activated", function(host) if not original:contains(host) then local path = path_pattern:format(host); if not stat(path) then local fh, err = io.open(path, "w"); if fh then fh:write(("VirtualHost%q\n"):format(host)); module:fire_event("host-persisted", { host = host, file = fh }); fh:close(); module:log("info", "Config file for host '%s' created", host); else module:log("error", "Could not open '%s' for writing: %s", path, err or "duno"); end else module:log("debug", "File '%s' existed already", path); end else module:log("debug", "VirtualHost '%s' existed already", host); end end);