Control-W word erase on tcsh command line
Hello, Using the latest Cygwin under Win98 and Win2k (though this has occured in all versions of Cygwin I've used). When I try to use a Control-W under tcsh it erases the entire line instead of just the previous word. It happens whether I'm in the console or using an xterm (rxvt). It works properly when using bash. I'm using the tcsh that came with the Cygwin update (6.11.00). Here is the version info: version tcsh 6.11.00 (Astron) 2001-09-02 (i386-intel-posix) options 8b,dl,al,rh,color Is there an option that I can set to make it work? Or perhaps a termcap entry that needs to be modified? Thanks for any info. Steve -- Steve Chew - [EMAIL PROTECTED] - http://www.interzone.com Men go abroad to wonder at the height of mountains, at the huge waves of the sea, at the long courses of the rivers, at the vast compass of the ocean, at the circular motion of the stars; and they pass by themselves without wondering. -- Saint Augustine -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Control-W word erase in tcsh
Hello, Using the latest Cygwin under Win98 and Win2k (though this has occured in all versions of Cygwin I've used). When I try to use a Control-W under tcsh it erases the entire line instead of just the previous word. It happens Default setting in tcsh. whether I'm in the console or using an xterm (rxvt). It works properly when using bash. Is there an option that I can set to make it work? Or perhaps a termcap entry that needs to be modified? Did you try `man tcsh'? Sigh. OK, sometimes I'm an idiot. :) I always thought that the word-erase was set by stty, but that's not the case in tcsh. Instead it needs bindkey. Thanks for the pointer. Steve -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: SSH -R problem
Corinna Vinschen wrote: On Tue, Apr 09, 2002 at 11:48:56PM -0400, Steve Chew wrote: Everything works OK at first but after enough sessions are made across the SSH tunnel, I can no longer open sockets and other network programs on the Cygwin system (such as IE) fail. If I create enough sessions the entire system can hang. [...] One symptom of the problem is that after each session I end up with an extra socket in the LISTEN state on the Cygwin box (use netstat -an to check the socket states). I don't know why there would even be any sockets in the LISTEN state on the Cygwin box since the ssh client shouldn't have to do a listen. I can reproduce it on XP. An strace output shows nothing strange. Especially listen() is never called (otherwise it would show up in strace). I must assume that this is one of several annoying problems in Winsock. I've no idea why a socket is going into LISTEN state under these circumstances. Baffled, Corinna Thank you for the swift response! Are you saying that the problem is the the Windows 98 Winsock code? Lovely... How would you suggest narrowing down the problem? While I'm at it do you have any suggestions for a work-around? I've been considering ways of stopping and starting the SSH tunnel, but I'd rather not. I haven't yet looked into whether I can avoid the problem by using 'ssh -L' and changing the remote side to listen for an initial connection. That model doesn't work as well for what I want to do unfortunately. Also baffled, Steve -- Steve Chew - [EMAIL PROTECTED] - http://www.interzone.com Bother said Pooh. Eeyore, load two photon torpedoes and lock phasers on the Heffalump. Piglet, meet me in transporter room two. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
SSH -R problem
Hello, I've found a problem when running OpenSSH under Cygwin on Win98. The problem occurs when using the ssh -R option to do port forwarding from a remote host to my local machine. The remote machine is a Linux box running OpenSSH sshd. Everything works OK at first but after enough sessions are made across the SSH tunnel, I can no longer open sockets and other network programs on the Cygwin system (such as IE) fail. If I create enough sessions the entire system can hang. By sessions, I mean the following: - I open a connection with telnet (or whatever) across the SSH tunnel - I then close the connection before opening a new connection. - So, there should be no open sockets after each session. One symptom of the problem is that after each session I end up with an extra socket in the LISTEN state on the Cygwin box (use netstat -an to check the socket states). I don't know why there would even be any sockets in the LISTEN state on the Cygwin box since the ssh client shouldn't have to do a listen. What ends up happening is that I keep accumulating extra sockets in the LISTEN state (one for each session). I believe that Cygwin + ssh -R are combining to use up all of the file descriptors on the system due to the extra sockets in the LISTEN state. I have installed the latest Cygwin binaries and it still happens. A similar problem happens on Windows 2000. But, it only happens on Win2k when there is no server listening for connections on the Cygwin box. This problem does *not* happen when using OpenSSH on Solaris. The results of a cygcheck are at this URL: http://www.interzone.com/Personal/cygwin.info I went ahead and got the source code for OpenSSH and put some debugging output into it to see if it was inadvertently doing a listen() but as far as I could tell it wasn't. Has anyone else seen this problem? I find the problem pretty debilitating since I want to run the tunnel to my local server for a long period of time and use a lot of connections but it ends up hanging the system. Any help would be appreciated. :) Steve [EMAIL PROTECTED] P.S. Another issue that may be related is that when there is no server on the Cygwin box listening for connections across the SSH tunnel I would expect that a telnet across the tunnel would result in a Connection Refused message. This is what happens when using Solaris instead of Cygwin. Instead, the connection just hangs until it is killed. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
