[asterisk-bugs] [Asterisk 0017160]: CLI prompt interfers with CLI output
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Apr 12 10:09:27 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17160
======================================================================
Reported By: coolmig
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17160
Category: Core/General
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.6.2.7-rc1
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-04-09 16:20 CDT
Last Modified: 2010-04-12 10:09 CDT
======================================================================
Summary: CLI prompt interfers with CLI output
Description:
Some characters of the CLI prompt are printed in the asterisk CLI output:
virtual2_ast2*CLI> cdr show status
virtual2_ast2*CLI>
Call Detail Record (CDR) settings
----------------------------------
Logging: Enabled
Mode: Simple
Log unanswered calls: No
* Registered Backends
-------------------
csv2_ast2*CLI> <<<-- Here
cdr-customCLI> <<<-- Here
pgsqlast2*CLI> <<<-- Here
virtual2_ast2*CLI> core show channels
Channel Location State Application(Data)
0 active channels>
0 active callsCLI> <<<-- Here
0 calls processed>
virtual2_ast2*CLI>
This happens in a lot of commands.
Looks like in certain cases, when the line string has less than the CLI
prompt characters, the remaining characters are printed. This makes output
unclean.
======================================================================
----------------------------------------------------------------------
(0120273) lmadsen (administrator) - 2010-04-12 10:09
https://issues.asterisk.org/view.php?id=17160#c120273
----------------------------------------------------------------------
I've seen the same thing as well (I haven't reproduced this issue right
now), so it likely has something to do with which shell and terminal is
being used.
Issue History
Date Modified Username Field Change
======================================================================
2010-04-12 10:09 lmadsen Note Added: 0120273
======================================================================
More information about the asterisk-bugs
mailing list