Bug#479375: asterisk console screws up terminal subtly when exited with ctrl-c

Tzafrir Cohen tzafrir.cohen at xorcom.com
Thu Sep 11 13:36:27 UTC 2008


On Sun, May 04, 2008 at 05:48:44PM +0300, Tzafrir Cohen wrote:

> I tried comparing the output of 'stty -a' at the following:
> 
> 1. Clear start ("sane")
> 2. Starting Asterisk from zsh and pressing ctrl-C ("zshbad")
> 3. Starting Asterisk from bash and pressing ctrl-C ("bashbad").
> 
> No noticable differences between "sane" and "bashbad". The differences
> between "sane" and "zshbad" are:
> 
> 	sane	zshbad
> 	----    ------
> eof     ^D      <undef>	
> rprnt   ^R      <undef>
> werase  ^W      <undef>	
> lnext   ^V      <undef>
>       -inlcr    inlcr
>       iexten	-iexten
>       echok     -echok

Update: still reproducable:

asterisk              1:1.4.21.2~dfsg-1+b1

bash                  3.2-4
busybox-static        1:1.10.2-1
dash                  0.5.4-11
posh                  0.6.13
zsh                   4.3.6-6

mlterm                2.9.4-4

posh and bash work well. zsh, dash and busybox ash mis-behave: leave 
'eof' undefined. With dash and busybox ash, after pressing ctrl-C you 
can no longer write to the terminal (until a 'clear' or 'stty sane').

Note, the terminal I tested this today with was mlterm, which I
sometimes suspect of misbehaving on its own.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir





More information about the Pkg-voip-maintainers mailing list