[asterisk-bugs] [JIRA] (ASTERISK-26031) contrib: RHEL init script does not show "OK" or "ERROR" on start

[Joshua Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp updated ASTERISK-26031:
-----------------------------------

    Summary: contrib: RHEL init script does not show "OK" or "ERROR" on start  (was: RHEL init script does not show "OK" or "ERROR" on start)

> contrib: RHEL init script does not show "OK" or "ERROR" on start
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-26031
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26031
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Contrib/General
>            Reporter: Michael Newton
>            Severity: Minor
>
> 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}



--
This message was sent by Atlassian JIRA
(v6.2#6252)