[asterisk-bugs] [JIRA] (ASTERISK-28158) Some conditions prevent running of el_end, break the terminal.

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=245410#comment-245410 ] 

Asterisk Team commented on ASTERISK-28158:
------------------------------------------

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].

> Some conditions prevent running of el_end, break the terminal.
> --------------------------------------------------------------
>
>                 Key: ASTERISK-28158
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28158
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Configuration, Core/General
>    Affects Versions: 13.23.1, GIT, 16.0.0
>            Reporter: Corey Farrell
>            Severity: Minor
>
> {{el_end}} is not always run when exiting Asterisk processes.  This can cause the terminal to be broken.  I've found two situations where this occurs:
> * {{console=yes}} set in {{asterisk.conf}}, {{rasterisk -x}} piped to another utility breaks the terminal which ran rasterisk.  I could only reproduce this in CentOS 7, it doesn't seem to happen in Fedora 28.
> * Asterisk daemon started at command-line with console enabled via config or command-line, {{rasterisk -x 'core stop now'}}.  This leaves the terminal which started the daemon in a broken state.
> As a partial work-around you can run {{reset}} from the broken terminal to fix it.
> Original report at https://community.asterisk.org/t/asterisk-16-piped-rx-breaks-shell/77061/



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