This is the mail archive of the
mailing list for the Cygwin project.
Re: Problems with cygwin cvs over ssh.
On 25/01/06, Karl-Heinz Wirth <firstname.lastname@example.org> wrote:
> >On Wed, 25 Jan 2006, James Courtier-Dutton wrote:
> > CVS_RSH=/bin/ssh
> > CVS -d email@example.com:/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.
local $ ssh user@host
host $ run-script <- This displays output correctly on local.
host $ exit
local $ ssh user@host 'run-script' <- No output displayed.
To be more exact, we were nesting the ssh commands, i.e. run-script
contained a "ssh user2@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.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html