[asterisk-bugs] [Asterisk 0017222]: [patch] Colourized logging option request as an option

Asterisk Bug Tracker noreply at bugs.digium.com
Wed May 12 13:04:23 CDT 2010


The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17222 
====================================================================== 
Reported By:                voxter
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17222
Category:                   Core/General
Reproducibility:            have not tried
Severity:                   feature
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.2.7-rc2 
JIRA:                        
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             2010-04-21 14:03 CDT
Last Modified:              2010-05-12 13:04 CDT
====================================================================== 
Summary:                    [patch] Colourized logging option request as an
option
Description: 
I noticed that recently there was a patch submitted to remove colorized
escape sequences from log files,
https://issues.asterisk.org/view.php?id=16786

The decision was made to not offer this as an option, however, I find it
incredibly useful when debugging certain features to retain color codes in
the log files to read it easier.  This being suddenly gone, could be
considered a regression.

On IRC, Naikrovek mentioned that a recent discovery was made correlating
writing color codes to log files with CPU spikes.  Of course, if this is
infact the case, it should not be added as an option until the CPU spike is
solved (if it is possible to be solved, of course)

But, on the grounds that it was once an available feature, that I welcomed
and took advantage of for debugging purposes, I would like to see it
re-introduced as a configurable option.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016786 [patch] Remove coloring escape sequence...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-12 13:04 pabelanger     Resolution               open => won't fix   
======================================================================




More information about the asterisk-bugs mailing list