X-Spam-Check-By: sourceware.org Message-ID: Date: Wed, 25 Jan 2006 17:41:49 +0000 From: James Courtier-Dutton To: cygwin AT cygwin DOT com Subject: Re: Problems with cygwin cvs over ssh. In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k0PHgCHV026108 On 25/01/06, Karl-Heinz Wirth wrote: > Hi > > >On Wed, 25 Jan 2006, James Courtier-Dutton wrote: > > > CVS_RSH=/bin/ssh > > CVS -d fred AT x DOT x DOT x DOT x:/test-repository co test1 > > ...password.... > > cannot mkdir /tmp/cvs-server1396/. > > No such file or directory. > > I am having the same problem now, after upgrading > to cygwin 1.5.19-4 from 1.5.18-1. > > I am working with the Eclipse IDE on Windows which uses cygwins cvs and ssh in > the background > > > So, the problem is the ssh and cvs combined. > > If I ssh, then run cvs it checks out fine. The problem is getting the > > information back through the ssh pipe. > > cvs with ssh works fine in my installation, if i reinstall cygwin 1.5.18-1. > > So, going back to cygwin 1.5.18-1 is my current workaround. > For those that might be interested, my current work around is to uninstall cygwin cvs and use CVSNT instead on the server. So, it looks very much like a cygwin cvs problem at the moment. Although, on another project where we were using ssh to run scripts remotely and return the output, the script was running fine, but the output never reached back. This points me towards a problem with openssh on cygwin. It might be a problem with pipes under cygwin, as I assume it is the unix feature of pipes that redirects the output from commands back through the ssh session. E.g. This works: local $ ssh user AT host host $ run-script <- This displays output correctly on local. host $ exit This fails: local $ ssh user AT host 'run-script' <- No output displayed. To be more exact, we were nesting the ssh commands, i.e. run-script contained a "ssh user2 AT host2 'run-script2' line. It was the output from this nested ssh that failed to be returned. When I get a moment, I will try to post some example scripts to demonstrate the problem. James -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/