Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com X-Originating-IP: [24.0.161.175] From: "Karl M" To: cygwin AT cygwin DOT com Subject: ssh hanging Date: Thu, 17 May 2001 22:28:38 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 18 May 2001 05:28:38.0704 (UTC) FILETIME=[6478F300:01C0DF5B] Hi Corinna... I started digging into this and found that ssh -v -v -v -f localhost sleep 10 with a sshd -d -d -d run from an interactive bash shell hangs on both 2.9p1-1 and 2.5.2p2-3 at the same place. The place is just after the protocol window is adjusted. While, for me (win2k sp1, 1.3.1-1 dll), ssh -v -v -v -f -L 5901:localhost:5900 localhost sleep 10 works fine with 2.5.2p2-3 but hangs with 2.9p1. When it hangs, the printout looks identical to the hanging cases above. It looks to me like protocol packets just stop getting received. I am running protocol 2 only. You and I also had the differnece that I needed pipes and you did not. Could this be related? I tried the May 16 snapshot with the same results. What configuration did you test with? Im not quite sure how to proceed further. I get the same results on three different machines. Why do you think that I need pipes and you do not? Thanks, ...Karl _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple