[asterisk-bugs] [Asterisk 0012720]: setting displayconnects=no still results in connection related messages (Parsing)

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12720 
====================================================================== 
Reported By:                p_lindheimer
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12720
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.20 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-24-2008 22:34 CDT
Last Modified:              05-25-2008 11:25 CDT
====================================================================== 
Summary:                    setting displayconnects=no still results in
connection related messages (Parsing)
Description: 
when setting displayconnects=no in manager.conf, one would expect no more
connection messages displayed at the CLI. Although the connection messages
are not displayed, there is still a line printed for each manager.conf file
and included files displayed during every connection at the CLI. Example:

  == Parsing '/etc/asterisk/manager.conf': Found
  == Parsing '/etc/asterisk/manager_additional.conf': Found
  == Parsing '/etc/asterisk/manager_custom.conf': Found

In the case of manager.conf and 2 include files within it. This results in
this setting not really achieving it's intended purpose. This can be very
distracting with installations that have many clients connecting and
disconnecting from the manager or even a single client polling it
regularly.
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 05-25-08 11:25  
---------------------------------------------------------------------- 
This actually is not a problem anymore in 1.6, because we parse
manager.conf only at load time, not at connect time.  While I understand
your frustration, those messages are being printed in an entirely different
section of the code, and any change to suppress those message would be a
very large hack, which I am not in favor of doing in any release code, as
1.4 is.  If it really bothers you on the console, I'd have to suggest using
'core set verbose 2', to lower the verbosity level.  Other than than,
there's nothing else that we are likely to consider doing, at least as far
as 1.4 is concerned.  As I said, 1.6 no longer does this. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-25-08 11:25  Corydon76      Note Added: 0087306                          
======================================================================