From 6a2f7b87d4fb19f30f64ede4b18582eb366c8b7d Mon Sep 17 00:00:00 2001
From: Luke Bratch <luke@bratch.co.uk>
Date: Wed, 12 Jun 2019 23:38:36 +0100
Subject: Allow reloading the configuration file at runtime using a BLABOUNCER
 command or by issuing the SIGHUP signal.

---
 README | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

(limited to 'README')

diff --git a/README b/README
index c399a62..2a861c5 100644
--- a/README
+++ b/README
@@ -22,12 +22,27 @@ An example configuration file is provided named "blabouncer.conf".
 
 If you don't specify one using "-c /path/to/configuration/file" then the example configuration one will be created for you in $HOME/.blabouncer/ when starting.
 
+Certain configuration options can be changed at runtime, either at any time, or by issuing a BLABOUNCER REHASH command or by sending SIGHUP to blabouncer.
+
+These options can be changed at any time as they are re-read when needed:
+ - nick2
+ - nick3
+ - password
+
+These options can be changed by issuing a BLABOUNCER REHASH command or by sending SIGHUP to blabouncer:
+ - replaymode
+ - replayseconds
+ - logging
+ - replaylogging
+ - debug
+
 == Commands ==
 
 Once connected to blabouncer with a client, you can use the following commands:
 
 "BLABOUNCER REPLAY [[[[days:]hours:]minutes:]seconds]" (To replay a given length of time of replay log.)
 "BLABOUNCER QUIT [quit message]" (To quit blabouncer, optionally sending [quit message] to the server.)
+"BLABOUNCER REHASH" (To reload settings from the configuration file, see above for details.)
 
 Blabouncer commands are all prefixed with BLABOUNCER which you can usually send using "/QUOTE BLABOUNCER".
 
-- 
cgit v1.2.3