From e76443455fef3e40366af261de10406d40bd64e0 Mon Sep 17 00:00:00 2001 From: antirez Date: Thu, 19 Dec 2013 16:02:24 +0100 Subject: [PATCH] Clarify include directive behavior in example redis.conf. --- redis.conf | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/redis.conf b/redis.conf index 4c18120e1..7fb4e4953 100644 --- a/redis.conf +++ b/redis.conf @@ -20,8 +20,12 @@ # other files, so use this wisely. # # Notice option "include" won't be rewritten by command "CONFIG REWRITE" -# from admin or Redis sentinel, you'd better put this option at the -# beginning of this file to avoid overwriting config change at runtime. +# from admin or Redis Sentinel. Since Redis always uses the last processed +# line as value of a configuration directive, you'd better put includes +# at the beginning of this file to avoid overwriting config change at runtime. +# +# If instead you are interested in using includes to override configuration +# options, it is better to use include as the last line. # # include /path/to/local.conf # include /path/to/other.conf