diff options
author | Richard Mudgett <rmudgett@digium.com> | 2014-01-14 18:14:02 +0000 |
---|---|---|
committer | Richard Mudgett <rmudgett@digium.com> | 2014-01-14 18:14:02 +0000 |
commit | 828f339a9cb52cdcb62c28962d87a5187dc7c5bc (patch) | |
tree | 0081ea00504678b5bc432cbdad91ba77493b4dab /UPGRADE.txt | |
parent | aced8bdd2e5d210f024be602bf5a1e70555ecec4 (diff) |
verbosity: Fix performance of console verbose messages.
The per console verbose level feature as previously implemented caused a
large performance penalty. The fix required some minor incompatibilities
if the new rasterisk is used to connect to an earlier version. If the new
rasterisk connects to an older Asterisk version then the root console
verbose level is always affected by the "core set verbose" command of the
remote console even though it may appear to only affect the current
console. If an older version of rasterisk connects to the new version
then the "core set verbose" command will have no effect.
* Fixed the verbose performance by not generating a verbose message if
nothing is going to use it and then filtered any generated verbose
messages before actually sending them to the remote consoles.
* Split the "core set debug" and "core set verbose" CLI commands to remove
the per module verbose support that cannot work with the per console
verbose level.
* Added a silent option to the "core set verbose" command.
* Fixed "core set debug off" tab completion.
* Made "core show settings" list the current console verbosity in addition
to the root console verbosity.
* Changed the default verbose level of the 'verbose' setting in the
logger.conf [logfiles] section. The default is now to once again follow
the current root console level. As a result, using the AMI Command action
with "core set verbose" could again set the root console verbose level and
affect the verbose level logged.
(closes issue AST-1252)
Reported by: Guenther Kelleter
Review: https://reviewboard.asterisk.org/r/3114/
........
Merged revisions 405431 from http://svn.asterisk.org/svn/asterisk/branches/11
........
Merged revisions 405432 from http://svn.asterisk.org/svn/asterisk/branches/12
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@405436 65c4cc65-6c06-0410-ace0-fbb531ad65f3
Diffstat (limited to 'UPGRADE.txt')
-rw-r--r-- | UPGRADE.txt | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/UPGRADE.txt b/UPGRADE.txt index 0fe7f6b7d..5e5931114 100644 --- a/UPGRADE.txt +++ b/UPGRADE.txt @@ -21,7 +21,31 @@ === UPGRADE-12.txt -- Upgrade info for 11 to 12 =========================================================== +From 12 to 13: +* The per console verbose level feature as previously implemented caused a + large performance penalty. The fix required some minor incompatibilities + if the new rasterisk is used to connect to an earlier version. If the new + rasterisk connects to an older Asterisk version then the root console verbose + level is always affected by the "core set verbose" command of the remote + console even though it may appear to only affect the current console. If + an older version of rasterisk connects to the new version then the + "core set verbose" command will have no effect. +CLI commands: + - "core show settings" now lists the current console verbosity in addition + to the root console verbosity. + + - "core set verbose" has not been able to support the by module verbose + logging levels since verbose logging levels were made per console. That + syntax is now removed and a silence option added in its place. + +Configuration Files: + - The 'verbose' setting in logger.conf still takes an optional argument, + specifying the verbosity level for each logging destination. However, + the default is now to once again follow the current root console level. + As a result, using the AMI Command action with "core set verbose" could + again set the root console verbose level and affect the verbose level + logged. =========================================================== =========================================================== |