[Asterisk-Dev] recent patch for set debug and set verbose
Christopher L. Wade
clwade at sparco.com
Fri Oct 8 07:14:19 MST 2004
Mark,
Modified Files:
cli.c pbx.c
Log Message:
Fix small verboseness bugs (bug #2602)
This does not completely fix the bug, follow this...
==========================================================
asterisk*CLI> set debug 0
Core debug is now OFF
asterisk*CLI> extensions reload
== Parsing '/etc/asterisk/extensions.conf': Found
[snip 11 more 'Parsing' lines...]
-- Setting global variable 'PROTO' to 'SIP'
[snip 11 more 'Setting' lines...]
-- Registered extension context 'default'
-- Added extension '_80[1-5]' priority 1 to default
[snip 8 more 'Added' lines...]
[snip 154 more mixed 'Registered' and 'Added' lines...]
-- Including context 'default' in context 'internal'
[snip 2 more 'Including' lines...]
asterisk*CLI> set debug 25
Core debug was 0 and is now 25
asterisk*CLI> extensions reload
-- Setting global variable 'PROTO' to 'SIP'
[snip 11 more 'Setting' lines...]
-- Including context 'default' in context 'menu-main'
[snip 3 more 'Including' lines...]
asterisk*CLI>
==========================================================
All total, output with set debug 0 is 191 lines for my setup, but with
set debug above 0, output is 16 lines.
Also, if memory serves correctly, debug being anything above 0 caused
*tons* more output from asterisk. Basically, what I remember seing
before the 'set debug' command was added was that on fully utilized
system, with asterisk started with -vvvvvvvvvvvvvvvvvdddddddddddddddd my
screen would scroll by so fast I had to turn on scroll lock and scroll
back just to see what was going on. Now, debug only makes asterisk as
silent as it was when I do set verbose 0.
Thanks,
Chris
--
Christopher L. Wade Unistar-Sparco Computers, Inc.
Senior Systems Administrator dba Sparco.com
Email: clwade at sparco.com 7089 Ryburn Drive
Phone: (901) 872 2272 / (800) 840 8400 Millington, TN 38053
Fax: (901) 872 8482 USA
More information about the asterisk-dev
mailing list