|Summary:||ASTERISK-15098: [patch] Backport patch 9048 to v1.4: Provide colors for daemonized asterisk|
|Reporter:||Humberto Diógenes (hdiogenes)||Labels:|
|Date Opened:||2009-11-06 17:30:16.000-0600||Date Closed:||2009-11-11 10:09:40.000-0600|
|Environment:||Attachments:||( 0) asterisk-1.4-color.patch|
|Description:||Bug 9048 still happens in Asterisk 1.4.26: no color in rasterisk if asterisk was daemonized.|
****** ADDITIONAL INFORMATION ******
Sorry for opening a duplicate bug, but I did not find a way to report this issue on the existing one.
|Comments:||By: Tilghman Lesher (tilghman) 2009-11-08 12:03:48.000-0600|
By: Humberto Diógenes (hdiogenes) 2009-11-10 15:51:37.000-0600
The comment on r88437 is "Revert commit #86119. Some users intentionally do not want colorized terminals, so this was a misfeature."
With this patch, users that don't want colorized terminals can just run `rasterisk -n` or `asterisk -n`.
-n Disable console colorization
In the other hand, the way Asterisk runs today will enable color only if started in console mode. AFAIK most Asterisk users run it in daemon mode, and not accepting this patch leaves users who *want* color with no option other than to never start asterisk in daemon mode.
I think that the option to use color or not should be made at the time the user runs `rasterisk`, not at server boot.
By: Tilghman Lesher (tilghman) 2009-11-11 09:13:21.000-0600
Even if so, this is not a candidate for inclusion for 1.4 or in any released version of Asterisk, as it changes behavior.
By: Tilghman Lesher (tilghman) 2009-11-11 10:09:40.000-0600
If you want to reopen issue ASTERISK-8789, please start a discussion on the asterisk-dev mailing list, making your case there. We will conform to the community thoughts on that forum. Reopening this issue is a non-starter, as 1.4 is not a candidate for this change.