Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: Jeff Mincy MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15278.40307.70000.268052@antarres.muniversal.com> Date: Sun, 23 Sep 2001 22:41:55 -0400 To: David Starks-Browning Cc: Joo-won Jung , cygwin@cygwin.com Subject: cvs + ssh freezes In-Reply-To: <5665-Sun23Sep2001205847+0100-starksb@ebi.ac.uk> References: <5665-Sun23Sep2001205847+0100-starksb@ebi.ac.uk> X-Mailer: VM 6.95 under 21.4 (patch 3) "Academic Rigor" XEmacs Lucid From: David Starks-Browning Date: Sun, 23 Sep 2001 20:58:47 +0100 On Sunday 23 Sep 01, Joo-won Jung writes: > > Problem: When I try to use cvs using SSH, It does not finish. > > I'm using: cygwin 1.3.3-2, cvs 1.11.0-1, openssh 2.9p2-3 > on: Windows 98 SE Korean (4.10.2222 A) It came up on this mailing list just *7* days ago. Refer to the thread starting at . Time for a FAQ entry, I guess. You mean like?: http://sources.redhat.com/cygwin/faq/faq_5.html#SEC125 FWIW, this is the *one* bug that I would put as the most annoying. Any time I do a remote cvs operation I have to kill the cvs/ssh process. I can't use ^C at the shell prompt because that kills my emacs that is tunnelled through ssh to my work machine. So I have to do the old control-alt-delete thing to kill the ssh. At this point I would settle for a hack that would allow ssh to 'work'. For example, some sort of timeout on the select call, perhaps set from an environment variable. -jeff -- 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/