view mod_reload_modules/README.markdown @ 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 4d73a1a6ba68
children
line wrap: on
line source

---
labels:
- 'Stage-Stable'
summary: Automatically reload modules with the config
...

Introduction
------------

By default Prosody does not reload modules at runtime unless instructed
to via one of its admin interfaces. However sometimes you want to easily
reload a module to apply new settings when the config changes.

mod\_reload\_modules will reload a set list of modules every time
Prosody reloads its config (e.g. on SIGHUP).

Configuration
-------------

Add "reload\_modules" to modules\_enabled. Then the list of modules to
reload using the 'reload\_modules' option in your config like so:

    reload_modules = { "groups", "tls" }

This would reload mod\_groups and mod\_tls whenever the config is
reloaded. Note that on many systems this will be at least daily, due to
logrotate.

Compatibility
-------------

  ----- -------
  0.9   Works
  ----- -------