cvs hangs with :ext: access
Hi
after trying with no success to access a cvs repository (cvs.sourceforge.net) via ssh (:ext:) I created a test repository on my own machine tried and to access it. The result is the same, cvs hangs for a while then quits saying "connection refused". tcpdump shows that cvs sends out requests but they remain unanswered. Things work with :pserver: Here is what happens when trying to access a remote repository; 09:39:12.838611 IP fax.org.1023 > cvs.sourceforge.net.shell: S 1938029198:1938029198(0) win 5840 <mss 1460,sackOK,timestamp 424626 0,nop,wscale 2> 09:39:15.838211 IP fax.org.1023 > cvs.sourceforge.net.shell: S 1938029198:1938029198(0) win 5840 <mss 1460,sackOK,timestamp 427627 0,nop,wscale 2> 09:39:21.837293 IP fax.org.1023 > cvs.sourceforge.net.shell: S 1938029198:1938029198(0) win 5840 <mss 1460,sackOK,timestamp 433627 0,nop,wscale 2> 09:39:33.835468 IP fax.org.1023 > cvs.sourceforge.net.shell: S 1938029198:1938029198(0) win 5840 <mss 1460,sackOK,timestamp 445627 0,nop,wscale 2> 09:39:57.831823 IP fax.org.1023 > cvs.sourceforge.net.shell: S 1938029198:1938029198(0) win 5840 <mss 1460,sackOK,timestamp 469627 0,nop,wscale 2> as you can see the cvs client sends out connection requests but sourceforge is not responding at all, the same happens with a local repository. Any ideas? |
Up!
I need cvs, better take this post visible ;-) |
Seeing same problem with Fedora Core 4
I can't help you solve this problem, as it just surfaced after I installed Fedora Core 4 on a dual-boot system. The other partition runs JDS 3 (Sun's Java Desktop System, a SuSE 9 derivative), and the shared project directory works fine (ie, cvs update) to the same repository, but hangs when FC4 is booted. The problem remains even after I copied the /etc/ssh and $HOME/.ssh from JDS to FC4. More mysterious is that "ssh <server>" works with both systems, just not CVS.
If I run "cvs -t <cmd>", it shows the hang is in "Starting server: rsh <server> cvs server". It turns out that *any* rsh command hangs, such as "rsh <server> ls", even though "ssh <server> ls" works fine. Any rsh experts out there? Tom |
Found it: set CVS_RSH to "ssh" (for bash, add "export CVS_RSH=ssh" to your .bash_profile).
http://www.linuxquestions.org/questi...hreadid=217992 |
All times are GMT -5. The time now is 05:22 AM. |