Date: Wed, 25 Jan 2017 11:26:09 +0100 From: "Martin S. Weber" <Ephaeton@gmx.net> To: Kurt Jaeger <lists@opsec.eu> Cc: "Eugene M. Zheganin" <emz@norma.perm.ru>, freebsd-stable@freebsd.org Subject: Re: reset not working like 70% of the time Message-ID: <20170125102609.GA1359@hephaistos.local> In-Reply-To: <20170125101517.GW13006@home.opsec.eu> References: <5888754F.2040901@norma.perm.ru> <20170125101517.GW13006@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-01-25 11:15:17, Kurt Jaeger wrote: > Hi! > > > does anyone suffer from this too ? Right now (and for several last > > years) a 100% decent way to reset a terminal session (for instance, > > after a connection reset, after acidentally displaying a binary file > > with symbols that are treated as terminal control sequence, after > > breaking a cu session, etc) is to launch midnight commander and then > > quit from it. And the reset is working like in 30% of cases only. > [...] > > Am I the only person seeing this ? > > I had some cases in the past where xterm was hanging, too -- but > not with *that* high rate of problems. > > Most of the times, xterm's Full Reset options works fine. > > The question is: how to debug that... ? Use script(1) to record an offending session, including the reset. Then replay with script or cat or ... Regards, -Martin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170125102609.GA1359>