Mike
2008-Apr-09 20:49 UTC
[asterisk-users] Jumped from 1.2.7 to 1.4.19, missing CLI colors
Hi, I`ve just made a leap from * 1.2.7 to 1.4.19. It took a while to fix all the deprecated stuff, but everything seems to be working fine now, except for a little tiny thing. I lost all color in my CLI, which makes it harder to debug. Is there something that needs doing? I didn't explicitely disable colorization from the command line, and I did try using nocolor=no in the config files. No luck. Regards, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080409/96ba16b6/attachment.htm
Mik Cheez
2008-Apr-09 23:05 UTC
[asterisk-users] Jumped from 1.2.7 to 1.4.19, missing CLI colors
Correct me if I'm wrong, but if you run asterisk as a service this happens. There is/was some dispute as to the fallacy of using 'safe_asterisk' anyway. Start it at the command line to see the pretty colors. Mike wrote:> Hi, > > I`ve just made a leap from * 1.2.7 to 1.4.19. It took a while to fix > all the deprecated stuff, but everything seems to be working fine now, > except for a little tiny thing. I lost all color in my CLI, which makes > it harder to debug. Is there something that needs doing? I didn't > explicitely disable colorization from the command line, and I did try > using nocolor=no in the config files. No luck. > > Regards, > > Mike > > > ------------------------------------------------------------------------ > > _______________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users
Anthony Francis
2008-Apr-10 02:15 UTC
[asterisk-users] Jumped from 1.2.7 to 1.4.19, missing CLI colors
Tzafrir Cohen wrote:> On Wed, Apr 09, 2008 at 08:00:38PM -0400, Mike wrote: > >> Ah, not bad. When I start asterisk with "/usr/sbin/asterisk -c" I get the >> colors, but if I start it without -c and then connect to the console using >> "/usr/sbin/asterisk -r" I get no color. >> >> Since I want this to be running in the background, how do I fix this so I >> get to have my cake and eat it too? >> > > The patch is rather trivial. Just make Asterisk pretend that it is > "vt100" (or whatever) if it is running as a service. > >I cant get color using asterisk -r on 1.2.17 or 18 either.
Joshua Kinard
2008-Apr-10 15:43 UTC
[asterisk-users] Jumped from 1.2.7 to 1.4.19, missing CLI colors
Seconded/thirded too. Went from 1.4.18 to 1.4.19, stopped using -c and went to background and connecting using -r, and colors disappeared for me as well. I'm using screen as well (ls -l --color=auto works fine in screen too). Is there a documented "fix" available, or is this more just an odd curiosity regarding termtypes? --J -----Original Message----- Sent: Wednesday, April 09, 2008 10:16 PM Tzafrir Cohen wrote:> On Wed, Apr 09, 2008 at 08:00:38PM -0400, Mike wrote: > >> Ah, not bad. When I start asterisk with "/usr/sbin/asterisk -c" I get the >> colors, but if I start it without -c and then connect to the console using >> "/usr/sbin/asterisk -r" I get no color. >> >> Since I want this to be running in the background, how do I fix this so I >> get to have my cake and eat it too? >> > > The patch is rather trivial. Just make Asterisk pretend that it is > "vt100" (or whatever) if it is running as a service. > >I cant get color using asterisk -r on 1.2.17 or 18 either.
Joshua Kinard
2008-Apr-10 16:48 UTC
[asterisk-users] Jumped from 1.2.7 to 1.4.19, missing CLI colors
Hmm, interesting, initially it wasn't working. Maybe I started it from outside of screen? Odd. BTW, is it possible for the SuSE script to support a variable to pass args to the daemon? Like perhaps modifying ASTARGS to be a changable param at the top of the script? I like the verbose output, and attempting to add it there myself (and change Line 71 to recognize its existence) didn't pan out right. Right now, I have to manually send "core set verbose 999" when connecting in. Thanks!, --J -----Original Message----- Sent: Thursday, April 10, 2008 12:10 PM Joshua Kinard wrote:> Seconded/thirded too. Went from 1.4.18 to 1.4.19, stopped using -c and went to background and connecting using -r, and colors disappeared for me as well. I'm using screen as well (ls -l --color=auto works fine in screen too). >The colors work if you use the supplied init scripts. cd /path/to/asterisk/source/contrib/init.d Doug -- Ben Franklin quote: "Those who would give up Essential Liberty to purchase a little Temporary Safety, deserve neither Liberty nor Safety." _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Joshua Kinard
2008-Apr-10 17:35 UTC
[asterisk-users] Jumped from 1.2.7 to 1.4.19, missing CLI colors
-----Original Message----- Sent: Thursday, April 10, 2008 1:08 PM> Or maybe it's plain buggy. Bug reports are welcomed.Nah, I think it was PEBKAC and PICNIC here :: sheepish grin :: I tried adding -vvvv-style options to the DAEMON var assignment, and it looks like the -f check further down didn't like that. I'll look into the sysconfig setting...more used to Gentoo setups than SuSE.> BTW: why do you prefer it to start verbosely? This tends to clutter the > logs with useless information.Oh, this is just for a faxing system. We have an ancient Rolm in place for the actual phone calls. I want to monitor/log things when I roll it out for testing to catch any oddities that may occur with inbound and outbound faxes. Communication between it and the Rolm sometimes went to "sleep" (I sent a mail here on that, but got no responses), and so, I want to watch for it in case it happens again. Might've been a bug fixed in the newer releases of zaptel and asterisk (which I'm running now). --J
Joshua Kinard
2008-Apr-10 17:37 UTC
[asterisk-users] Jumped from 1.2.7 to 1.4.19, missing CLI colors
-----Original Message----- Sent: Thursday, April 10, 2008 1:22 PM> 15? What do you need that for? > > IIRC the highest verbosity level is 5. anything more than that doesn't > change the clogging of your logs.Ah, 5 is max? Kinda like gcc not supporting anything greater than -O3? Good to know that. I figured -vvvvvvvv was overkill, but I hadn't dived into the options parsing code to actually verify that. --J
Apparently Analagous Threads
- Similar option as promiscredir to use in transfer (REFER)
- problems in REFER request to a different machine
- Dahdi Init script for Suse?
- (Critical Updates) Asterisk 1.2.27, 1.4.18.1, 1.4.19-rc3, 1.6.0-beta6 Released
- (Critical Updates) Asterisk 1.2.27, 1.4.18.1, 1.4.19-rc3, 1.6.0-beta6 Released