https://reviewboard.asterisk.org/r/1599/ I so wish that this patch would be backported to the 1.8 branch! I am considering switching to trunk just for this alone.
I know it's a stretch but, given the popularity of running Fail2Ban alongside Asterisk, could it not fall under the pretense of 'security risk' that someone very easily breaks Fail2Ban by forgetting to set verbose back to 5 during a routine CLI session where they might have temporarily needed to reduce verbosity? I know I'm reaching, but doesn't hurt to beg. Luke -----Original Message----- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tzafrir Cohen Sent: Saturday, December 31, 2011 5:06 AM To: asterisk-users@lists.digium.com Subject: Re: [asterisk-users] High verbose set at console effects the logger file "Full" - Why is that? On Fri, Dec 30, 2011 at 09:03:34PM -0500, Bruce B wrote: > So, based on what you are saying if I issue the command "core set > verbose 0" and then exit the system Fail2Ban will stop working for > Asterisk (this is since Fail2ban works based on the log file entries). > > Can anyone else please confirm that as well. Though in trunk you can set different log levels to different files. -- Tzafrir Cohen -- _____________________________________________________________________ -- 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
