Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 28 Feb 2001 18:36:04 -0800 (PST)
From:	Matt Linton <mlinton AT email DOT arc DOT nasa DOT gov>
To:	cygwin AT cygwin DOT com
Subject:	SSH in CVS
Message-ID:	<Pine.GSO.4.21.0102281832380.1991-100000@delerium.arc.nasa.gov>
MIME-Version:	1.0

Greetings, Cygwin developers. Before you kill this mail, I should state
that I've read the FAQ and the posting from Patrick Doyle explaining
exactly why Cygwin hangs and makes you type Ctrl-C to kill an SSH process
after using SSH to bring a CVS repository to your system.

My question is thus: A user in my department is attempting to use SSH to
access CVS, but is running that through automation. Thus, his automation
does not allow him the opportunity to manually break the bad fork, and his
automation has to be cut short each time he attempts to check out a CVS
binary.

Is there any fix, patch or workaround that has been discovered since
Patrick's posting to the mailing list? Or do you have any advice on how I
can help the users workaround this problem and still automate?

Many thanks in advance;

Matt Linton
Systems Administrator, Code IC:
NASA Ames Research Center


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -