ASTERISK-26031: contrib: RHEL init script does not show "OK" or "ERROR" on start

[Home]

Summary: ASTERISK-26031: contrib: RHEL init script does not show "OK" or "ERROR" on start

Reporter: Michael Newton (miken32) Labels:

Date Opened: 2016-05-17 13:20:31 Date Closed:

Priority: Minor Regression?

Status: Open/New Components: Contrib/General

Versions: Frequency of
Occurrence Constant

Related
Issues:

Environment: Attachments:

Description: If one has {{COLORS=yes}} defined in {{/etc/sysconfig/asterisk}} then the call to start Asterisk in the init script is subject to much redirection. As a result, it does not display the {{[ OK ]}} or {{[ ERROR ]}} message echo'd from the {{daemon}} function.

{code}
if [ "x$COLOR" = "xyes" ]; then
export TERM=linux
daemon sh -c "$DAEMON $ASTARGS -c" >/dev/null </dev/null 2>&1 &
else
daemon $DAEMON $ASTARGS
fi
{code}

No explanation was given for this change when it was made in ASTERISK-15322, and the point of the {{COLOR}} variable is fairly vague. My only guess is that it relates to colours showing on TTY9? It doesn't have anything to do with colours showing in the console when you connect with {{asterisk -r}}.

{noformat}
# If you DON'T want Asterisk to start up with terminal colors, comment
# this out.
COLOR=yes
{noformat}

Comments: By: Asterisk Team (asteriskteam) 2016-05-17 13:20:31.927-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].