A small clarification to keep bugs from being filed, and confusion from rising, if...

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/1.4@59452 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/configs/extensions.conf.sample b/configs/extensions.conf.sample
index dd6ba132927a06d09b75a228f6417792440ef88a..e50837cde674276d4808d721c511e72f613f27ac 100644 (file)
--- a/configs/extensions.conf.sample
+++ b/configs/extensions.conf.sample
@@ -43,6 +43,16 @@ writeprotect=no
 ; through reloads, and even if deleted from the extensions.conf or
 ; one of its included files, will remain set to the previous value.
 ;
+; NOTE: A complication sets in, if you put your global variables into
+; the AEL file, instead of the extensions.conf file. With clearglobalvars
+; set, a 'reload' will often leave the globals vars cleared, because it
+; is not unusual to have extensions.conf (which will have no globals)
+; load after the extensions.ael file (where the global vars are stored).
+; So, with 'reload' in this particular situation, first the AEL file will
+; clear and then set all the global vars, then, later, when the extensions.conf
+; file is loaded, the global vars are all cleared, and then not set, because
+; they are not stored in the extensions.conf file.
+;
 clearglobalvars=no
 ;
 ; If priorityjumping is set to 'yes', then applications that support