hcq/MaxScale
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix to bug 721: http://bugs.mariadb.com/show_bug.cgi?id=721

Browse Source 
Fixed documentation to mention SIGHUP instead of SIGTERM
This commit is contained in:
Markus Makela
2015-02-04 20:39:47 +02:00
parent 27ed69e7b4
commit 04ac381669
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Getting-Started/Configuration-Guide.md
View File

@ -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.