From owner-freebsd-stable@freebsd.org Wed Jan 25 10:26:25 2017 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D1B7CBF30D for ; Wed, 25 Jan 2017 10:26:25 +0000 (UTC) (envelope-from Ephaeton@gmx.net) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D57EC1AD1 for ; Wed, 25 Jan 2017 10:26:23 +0000 (UTC) (envelope-from Ephaeton@gmx.net) Received: from hephaistos.local ([79.208.137.127]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MC8iq-1cf6Di3npQ-008ql6; Wed, 25 Jan 2017 11:26:11 +0100 Received: by hephaistos.local (Postfix, from userid 1000) id BB0F9297CDF7; Wed, 25 Jan 2017 11:26:09 +0100 (CET) Date: Wed, 25 Jan 2017 11:26:09 +0100 From: "Martin S. Weber" To: Kurt Jaeger Cc: "Eugene M. Zheganin" , freebsd-stable@freebsd.org Subject: Re: reset not working like 70% of the time Message-ID: <20170125102609.GA1359@hephaistos.local> Mail-Followup-To: Kurt Jaeger , "Eugene M. Zheganin" , freebsd-stable@freebsd.org References: <5888754F.2040901@norma.perm.ru> <20170125101517.GW13006@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170125101517.GW13006@home.opsec.eu> User-Agent: Mutt/1.7.2 (2016-11-26) X-Provags-ID: V03:K0:p2su1w70nIm0HFLVYwFqNnpDHORTQUorG7uKOaI8Qb185AbVKyi 5QiyEId/PDPfYalOv8bEAdqm1EoBZDDKrPUCHT7o3is8AQci7BZa9ZKTED9kM+MjlC0cWQ6 1zLoqbhodEE/br8n2RcdDbkuQKEEdCup3Eiaza4k1nNn8LDU7R6nhxHG0P1AiYEXWrlcomH xNgwwBmluZTs3NlcoeEeg== X-UI-Out-Filterresults: notjunk:1;V01:K0:qZxT0pT8EOI=:TjefYQC6lcXE4FQVKJcjVu QdPY7e+xU24md0ODqIPtZ0PuDj+g0ybAIMOM4Gxn3I9W6TzB8VCUOeQrgo7IKHjna0TGOf6gH VjDHRWT5WE/hdEmkky2vmA5GM/BvtJ5BFqS2y7K/B7sj8wAeONwEtldd/yfYiefCS90XVgx7b 605vzRLQC9llyAJjFFZWUlQyCA3uIOOvQDT2cpF8t5YGJ7feH5L/Oukvbgg5V02Yf1FRtjkQt GHSdHW6/tv63PnEU9b1ihYbUpYL06ecpebcywr+71nQLS1G750bELZ58ejOGMv5HLkXXPEmbm ly/OyBHr3k8qjal5Xh+viMa/Gi1/47OhkmfVKcI2n+j5yinTKcwObbCgAiFbOXBtCLa5pNu+z iShrtU0w0A7vuVuy7Nvx1HntcZMwEUs+mY4ECmTM8wclQsbuWlfY9yw9HGWUz2YwG4h7cYMs2 CH7pdTwxS4laYznflHOUJfHdzbgdHPlz3x1wx29dw8R42mzw4YxSmqB0Gf6pTYb9ZPpl3GsZP zW1SNIdJO11+7YStxD1RqISCIMmOTEepTVqWI+Lp5QKbHMsNWWR39JpVCeq+3vcGubkXI4uyC J+1LDB7kywALnIFL/1LdlxtBH/YxJIDadrvF1/yfju9Ez2ecjhNYhEfK+n2gfPH1O+gCIyayH G7JSyuJXroDNRWoPUU8hbT8ePkRLBCA1HNIbrMzJjQUSgEXYQno+m9afTfiI6KoVQiyIAo2m9 /QAElQrfhcXz3lUchRk3tOGIhrhLPIPIq1rvqa6sx1W2I+3UsdnMnxiZwEj4p5eVH+LF9tFrr 3/JbVLxSyu/vUPaeu94cGHGzOSF9Lngh63Im+UTurmorWe4vE7gSraKKXp7ec311SD6O272Eq ET+ppFUIqx5QtTaD+GxgdS+AgsFXgSmNKjqLAzVP0T/qE9MVLzITkvehoWzkAa+cdMOW/lGzp sh0xl9MJuHjkxR5jT1FoNAgtSwPLEfuKEHW+VdWcdiuVYKV6kaIQ5arLWk/LogUD+6T/NpqLI nA== X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 10:26:25 -0000 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