diff options
| author | murf <murf@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-03-30 00:56:36 +0000 |
|---|---|---|
| committer | murf <murf@f38db490-d61c-443f-a65b-d21fe96a405b> | 2007-03-30 00:56:36 +0000 |
| commit | 9b58ce234b81070f69a8b7b5eb46630fb5643f89 (patch) | |
| tree | b107346fa2731a827e9b8ab0195df326907fee6a /configs | |
| parent | da7a6b7ba1d46a4884cb7365b6ed288fdd345d72 (diff) | |
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: http://svn.digium.com/svn/asterisk/branches/1.4@59452 f38db490-d61c-443f-a65b-d21fe96a405b
Diffstat (limited to 'configs')
| -rw-r--r-- | configs/extensions.conf.sample | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/configs/extensions.conf.sample b/configs/extensions.conf.sample index dd6ba1329..e50837cde 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 |