This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: SSH in CVS
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>,Matt Linton <mlinton at email dot arc dot nasa dot gov>
- Subject: Re: SSH in CVS
- From: Mark Paulus <mark dot paulus at wcom dot com>
- Date: Fri, 02 Mar 2001 08:22:31 -0700
- Reply-to: Mark Paulus <mark dot paulus at wcom dot com>
Not sure about the specifics of your problem, but for automating
things that don't want to be automated, you might want to
"explore expect". Expect is a scripting tool that allows
one to automate things that don't want to be automated.
Do a 'man expect' for lots of info. And if that is overwhelming,
but you think expect might do it for you, then you might want
to get the OReilly book, "Exploring Expect", by Don Libes,
who consequently is the developer of expect also.
On Wed, 28 Feb 2001 18:36:04 -0800 (PST), Matt Linton wrote:
>
>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
>
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple