Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Wed, 21 Jul 2004 16:53:04 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: ssh : commands not echoed back to terminal Message-ID: <20040721205304.GB24828@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Wed, Jul 21, 2004 at 03:50:34PM -0400, Mark Bohlman wrote: >Dave Korn wrote: >>>-----Original Message----- >>>From: cygwin-owner On Behalf Of Song Ken Vern-E11804 >>>Sent: 21 July 2004 03:51 >> >>>I find that whenever I keep a ssh session for long time (overnight), >>>and come back to it the next morning, I cannot seem to see anything I >>>type. >>> >>>I am using rxvt, with bash. >>> >>>Everything runs as normal, just that whatever I type is not seen on >>>screen. >>> >>>When I exit the session (local cygwin), it goes back to normal. >>> >>>Then I ssh into the same server, and everything is OK again, for a >>>while. >> >>I have no idea why this might be happening, but what happens if, when >>it goes invisible, you try entering the command "stty sane"? Does that >>restore your display? > >This may or may not be related: I've found that I can duplicate this >type of behavior by setting the CYGWIN environment variable AFTER I >start a bash shell. That's expected behavior. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/