I'm on your side but many Kannel users run in debug log level, and this particular information is the same every time - it doesn't change from request to request. It's a non essential patch just 'nice to have' for most.
On Saturday, 24 September 2016, Rene Kluwen <[email protected]> wrote: > I don’t agree completely with your reasoning. > > Either you want debug information or you don’t. > > Enabling debug information yields a lot of information. > > What about if you want to debug the mysql pool usage? > > > > Still +0 from me in case it’s redundant info. > > > > *Van:* devel [mailto:[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>] *Namens *Donald > Jackson > *Verzonden:* zaterdag 24 september 2016 12:03 > *Aan:* kannel_dev_mailinglist <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> > *Onderwerp:* [PATCH] Reduce logging in dbpool_mysql.c > > > > Hi there, > > > > This is a simple patch to reduce excessive logging output of dbpool_mysql.c > > > > As we know many people run their Kannel systems with debug logging enabled > so running with '-v 1' isn't a solution to this problem and I see no > benefit of having this repetitive logging. > > > > Thanks, > > Donald > -- Donald Jackson http://www.elite-sms-software.com http://www.ddj.co.za http://www.thearchitech.com donald(a)thearchitech.com
