This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ssh : commands not echoed back to terminal


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?


cheers, DaveK

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.
Start bash shell
$ export CYGWIN=tty
$ vi anyfile ; quit vi
$ ls [this is NOT echoed back].


Then running
$ stty sane
stty: standard input: unable to perform all requested operations
shows the above error message and changes nothing.

I know that to get CYGWIN properly set it needs to be done BEFORE starting the shell, but it seems to give me fits no matter what.
Have also tried doing "stty echoe" but get the same message and no changes.
-- Mark




--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]