[asterisk-commits] murf: branch 1.4 r59452 - /branches/1.4/configs/extensions.conf.sample

[asterisk-commits at lists.digium.com]

Author: murf
Date: Thu Mar 29 19:56:36 2007
New Revision: 59452

URL: http://svn.digium.com/view/asterisk?view=rev&rev=59452
Log:
A small clarification to keep bugs from being filed, and confusion from rising, if clearglobalvars is set, and globals are set in the AEL file. (9419)

Modified:
    branches/1.4/configs/extensions.conf.sample

Modified: branches/1.4/configs/extensions.conf.sample
URL: http://svn.digium.com/view/asterisk/branches/1.4/configs/extensions.conf.sample?view=diff&rev=59452&r1=59451&r2=59452
==============================================================================
--- branches/1.4/configs/extensions.conf.sample (original)
+++ branches/1.4/configs/extensions.conf.sample Thu Mar 29 19:56:36 2007
@@ -42,6 +42,16 @@
 ; If clearglobalvars is not set, then global variables will persist
 ; 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
 ;