From b8ea70215d6613965cd5cbba5a9bbc37b4f4676d Mon Sep 17 00:00:00 2001 From: Markus Makela Date: Wed, 4 Feb 2015 20:39:47 +0200 Subject: [PATCH] Fix to bug 721: http://bugs.mariadb.com/show_bug.cgi?id=721 Fixed documentation to mention SIGHUP instead of SIGTERM --- Documentation/Getting-Started/Configuration-Guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/Getting-Started/Configuration-Guide.md b/Documentation/Getting-Started/Configuration-Guide.md index 8741a760b..88ee17d30 100644 --- a/Documentation/Getting-Started/Configuration-Guide.md +++ b/Documentation/Getting-Started/Configuration-Guide.md @@ -1554,7 +1554,7 @@ password=61DD955512C39A4A8BC4BB1E5F116705 # Configuration Updates -The current MaxScale configuration may be updating by editing the configuration file and then forcing MaxScale to reread the configuration file. To force MaxScale to reread the configuration file a SIGTERM signal is sent to the MaxScale process. +The current MaxScale configuration may be updating by editing the configuration file and then forcing MaxScale to reread the configuration file. To force MaxScale to reread the configuration file a SIGHUP signal is sent to the MaxScale process. Some changes in configuration can not be dynamically applied and require a complete restart of MaxScale, whilst others will take some time to be applied.