Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <5.0.2.1.1.20011011083027.03c10218@64.71.142.4> X-Sender: peterk AT 64 DOT 71 DOT 142 DOT 4 X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 11 Oct 2001 08:39:55 -0700 To: "Harig, Mark A." From: Peter Kennard Subject: RE: CVS_RSH (solved) Cc: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Thanks, Problem solved. It was a command in my .bashrc on the server that failed only when it was in non-interactive startup. And because of the way the startup is executed it ended the ssh pipe. Thanks for all your time. If someone wants this written up for a FAQ I will be glad to help out. Though this is more of a CVS or Linux circumstance. BTW I'm very happy I finally bit the bullet and upgraded beyond cygwin_b20 !!! Peter K At 10:57 AM 10/11/2001 -0400, Harig, Mark A. wrote: >To troubleshoot this, try to simplify the problem by eliminating Cygwin >from the loop: > > 1) Login to your CVS server: > > $ ssh -l > > 2) Set your CVSROOT and CVS_RSH environment variables on your CVS >server at its shell prompt: > > $ >CVSROOT=:ext:@:/path/to/cvs/repos > $ export CVSROOT > $ CVS_RSH=/path/to/ssh > $ export CVS_RSH > $ cvs -t status > >If the problem is still occurring on your CVS server, it might help to >point to where the problem is coming from. The fact that you were able >to use the :pserver: access method makes me think that you are setting >up CVS to be confused between using the 'pserver' access method and >using the 'rsh' access method. You shouldn't be mixing the two methods. > >Good luck! > >-----Original Message----- >From: Peter Kennard [mailto:peterk AT livingwork DOT com] >Sent: Wednesday, October 10, 2001 6:01 PM >To: Harig, Mark A. >Cc: cygwin AT cygwin DOT com >Subject: RE: CVS_RSH > > >I thank you all for your help. I still don't know what is happening. >But >it doesn't look like a cygwin problem. > >On my server (a new debian install with a plain vanilla cvs install from > >it's distribution) OpenSSHD > >I can do a cvs login with a :pserver: cvs root (to the local subnet >interface) >and do all CVS operation this way. > >I can ssh login to any interface on the server from my wincvs box > >If I >export CVS_RSH=ssh >export CVSROOT=:ext:me AT address:/repository >export WINCVS=binmode > >I do "cvs -t checkout module" >I then enter the password to ssh, > ->cvs entering main loop (from trace) >then I get a cvs server "unexpected end of file" > >None of the system logs are altered by this other tha auth.log which >idicates a succesful ssh login. > > >At 03:45 PM 10/10/2001 -0400, Harig, Mark A. wrote: > >You can help yourself with your debugging if you use the '-t' (trace) > >CVS command option. For example, > > > > $ cvs -t status /my/cvs/file > > > >Also, don't forget to export the CVSROOT and CVS_RSH variables: > > > > $ CVSROOT=:ext:@:/path/to/repository > > $ export CVSROOT > > $ CVS_RSH=/usr/bin/ssh > > $ export CVS_RSH > > > >Good luck! > > > >-----Original Message----- > >From: Peter Kennard [mailto:peterk AT livingwork DOT com] > >Sent: Wednesday, October 10, 2001 10:24 AM > >To: nhv AT cape DOT com; cygwin AT cygwin DOT com > >Subject: RE: CVS_RSH > > > > > >I got it I think - seems to be a permissions problem on the server. > >If I log in as root it works to checkout the module. I get an "end of > >file" error from cvs as my lowly user. I still have to untangle it :) > > > >Thanks though -- 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/