[asterisk-users] Use safe_asterisk manually, you get colors in CLI. Crontab it, you don't.

[Tony Mountifield]

In article <20080511004113.f1989b38ea6175db3efe8e52dbe2a6b2.6f4997013e.wbe at email.secureserver.net>,
Mark Hamilton <mark.h at cage151.com> wrote:
> Colors in the CLI have helped me ignore notices/warnings, etc and
> concentrate better on stuff that I want to look out for during testing.
> 
> I've noticed that a simple restart would not bring back the colors in
> the CLI. Asterisk needs to either start on boot, or start by way of
> safe_asterisk to have colors in the CLI.
> 
> To top this, I always restart asterisk nightly.
> My restart script code:
> 
> #!/bin/bash

Try adding here:

export TERM=linux

> time=`date`
> echo "I ran at $time" >> /root/asterisklog
> /usr/sbin/asterisk -rx "stop now"
> /usr/sbin/safe_asterisk
> 
> This basically shows that safe_asterisk is being defined, YET everytime
> the restart script is executed by crontab, I don't see the colors.
> Unless ofcourse I manually stop now, and safe_asterisk.
> 
> What gives?
> I just want to have an auto restart, and CLI with colors!

Cheers
Tony
-- 
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org