Summary:ASTERISK-12080: setting displayconnects=no still results in connection related messages (Parsing)
Reporter:Philippe Lindheimer (p_lindheimer)Labels:
Date Opened:2008-05-24 22:34:35Date Closed:2008-05-25 11:25:52
Versions:Frequency of
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.


This issue has existed since at least 1.2. I discussed this with Jared Smith who encouraged me to post a bug so that the dev team might attempt to get this addressed as part of 1.6 and it would be really nice if 1.4 could also be considered.
Comments:By: Tilghman Lesher (tilghman) 2008-05-25 11:25:28

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.