From 9db0871c2fa82f323900b95063c31e4eaac77aee Mon Sep 17 00:00:00 2001 From: Jason Volk Date: Wed, 4 Apr 2018 12:01:44 -0700 Subject: [PATCH] construct: Minor README paragraph order. --- construct/README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/construct/README.md b/construct/README.md index 58e7068fa..c0b7b923f 100644 --- a/construct/README.md +++ b/construct/README.md @@ -23,6 +23,11 @@ event loop for execution at the next event slice. This is how signal safety is achieved. Furthermore, according to boost docs, when signals are used this way they can be compatible with windows environments. +##### SIGQUIT + +A `ctrl-\` to Construct will cleanly shut down the server. It will not generate +a coredump. + ##### SIGINT A `ctrl-c` to Construct will bring up the command line console interface. It @@ -42,11 +47,6 @@ A "HangUP" to Construct is only relevant to the command line console, and signals it to close like an `EOF`. The legacy functionality for reloading server configuration et al is moved to `SIGUSR1`. -##### SIGQUIT - -A `ctrl-\` to Construct will cleanly shut down the server. It will not generate -a coredump. - ##### SIGUSR1 This signal commands the server to reload and refresh various aspects of its