From 4d90d92e7c0235abbef9acc5b36614b670a1fea2 Mon Sep 17 00:00:00 2001 From: Andrei Ismail Date: Tue, 25 Aug 2015 00:25:26 +0300 Subject: [PATCH] #351 Added --reload explanation --- doc/configuration_system.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/configuration_system.md b/doc/configuration_system.md index 540ae52fb..fb12244ee 100644 --- a/doc/configuration_system.md +++ b/doc/configuration_system.md @@ -70,13 +70,14 @@ At a normal start-up, ProxySQL initializes its configuration from the persisted in-memory database. This is found in the "datadir" (usually the current working directory in which ProxySQL is ran). The filename for the database is named "proxysql.db". So, disk gets loaded into memory and then propagated towards the runtime configuration. -# Initial startup (or --initial flag) +# Initial startup (or --initial/--reload flag) At the initial start-up (or start-up done with --initial flag, which resets the -database by renaming the old one), the major difference from normal start-up is that the memory and runtime configuration gets populated from the config file. +At the initial start-up (or start-up done with --initial flag, which resets the database by renaming the old one), the major difference from normal start-up is that the memory and runtime configuration gets populated from the config file. -After this is done, the configuration is also persisted to the disk database, -which will be used for the next restarts. +After this is done, the configuration is also persisted to the disk database, which will be used for the next restarts. + +The difference between --reload and --initial is that --reload does not create a backup of the old configuration file, while --initial does. # Soft restart (via angel process)