diff options
author | Kim Alvefur <zash@zash.se> | 2019-01-06 12:14:42 +0100 |
---|---|---|
committer | Kim Alvefur <zash@zash.se> | 2019-01-06 12:14:42 +0100 |
commit | 39e24a4e7318865adc6318c607f3858b37601702 (patch) | |
tree | 423af223e3f20ea60b24ebd1686f000ab6ecd89a | |
parent | 9061782b9a97df2ef95437d632335ae67eb7ffb6 (diff) | |
download | prosody-39e24a4e7318865adc6318c607f3858b37601702.tar.gz prosody-39e24a4e7318865adc6318c607f3858b37601702.zip |
util.startup: Always reload logging after config (fixes #1284)
This chancged in 6e24a69b03af likely because of confusion about the
`reopen-log-files` event which was fired but never hooked.
-rw-r--r-- | util/startup.lua | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/util/startup.lua b/util/startup.lua index e92867dc..c101c290 100644 --- a/util/startup.lua +++ b/util/startup.lua @@ -87,6 +87,9 @@ function startup.init_logging() -- Initialize logging local loggingmanager = require "core.loggingmanager" loggingmanager.reload_logging(); + prosody.events.add_handler("config-reloaded", function () + prosody.events.fire_event("reopen-log-files"); + end); prosody.events.add_handler("reopen-log-files", function () loggingmanager.reload_logging(); prosody.events.fire_event("logging-reloaded"); |