From 684527fcfdd44e687452417f6fbfa24ab937891c Mon Sep 17 00:00:00 2001 From: Steve Murphy Date: Fri, 30 Mar 2007 01:16:22 +0000 Subject: [PATCH] Merged revisions 59452 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r59452 | murf | 2007-03-29 18:56:36 -0600 (Thu, 29 Mar 2007) | 1 line 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) ........ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@59453 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/extensions.conf.sample | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/configs/extensions.conf.sample b/configs/extensions.conf.sample index 2ac69964fb..076049cabd 100644 --- 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