Fair enough. Giving up on the backport to 1.8 or 10 for now, I had a thought for a kludge.
How about a shell script (scheduled with cron) that checks for any 'active' consoles -- any connected consoles where there has been user input within the last X minutes. If it finds none, then set the verbosity back to 5 (or whatever level you want). There are a few problems with this -- I couldn't find any way to: 1) query Asterisk for a count or list of console connections, much less 'active' ones 2) query Asterisk for the current verbosity level (without changing it) Am I barking up another wrong tree here? Anyone have any other ideas on how to solve this problem? -----Original Message----- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Matthew Jordan Sent: Thursday, February 16, 2012 8:06 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] High verbose set at console effects the logger file "Full" - Why is that? It's not in Asterisk 10, it's in the current trunk, which will eventually become Asterisk 11. The patch, while a very nice and useful enhancement, is unfortunately fairly intrusive. I can't see it becoming part of the Asterisk 1.8 or Asterisk 10 branches, given (a) the fact that it is certainly an improvement and not a bug fix, and (b) the risk involved in back-porting a patch of that magnitude and scope. Matthew Jordan Digium, Inc. | Software Developer -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
