Kelly Rued wrote:
> I have a session called SVNConnection saved in PuTTy which connects to
> the server through PuTTy fine. I can connect to the server fine by
> running plink SVNConnection from the command line with no error messages
> at all. If I run TortoisePlink.exe from the command line it throws only
> the same cryptic pop-up error as the TortoiseSVN client itself: “unable
> to write to standard output” in a win pop-up error box (even with the –v
> flag there is no info in the DOS window).
> I found the solution of changing the ssh client in the Tortoise settings
> to the TortoisePlink.exe and have done so already, but before I did that
> I had PuTTy as the target and I was getting invalid port number errors
> (no idea if that helps or not). PuTTy is connecting to port 22 (the ssh
That's your hint ;)
You see: TortoisePlink is a modified plink which avoids popping up the
DOS window for every connection. The problem with that approach, even
though it is very convenient for users, is that error messages thrown
out by plink have nowhere to go to (the DOS window isn't there). So the
error message "unable to write to standard output" is plinks way to tell
you that it would have written a detailed error message to the DOS box,
but it couldn't since that box isn't there.
In such cases, you have to replace TortoisePlink with the normal plink
in the TSVN settings. Then plink will show you the errors in the DOS box.
Since you already did that once, you now know that there are 'port
number errors' as you say. You must solve those errors before you can
> port) and the ssh server is supposedly on 3690 so I’m not sure if that’s
> the issue. Also, I checked if the svnserve bin was available to the user
> name by logging in as the user through the saved PuTTy session and
> typing “which svnserve” (it returned the correct path so I assume that
> means it knows how to find the binaries for the svn stuff).
I personally don't use svn+ssh because I think https:// is just easier
to set up and use. So I can't really help you here with your setup.
> How can I get a more detailed error message from TortoisePlink? Also,
> how can I verify that svnserve is actually working on port 3690 as I set
> it up? I’m a newb to both subversion and tortoise- any info is greatly
> appreciated. J
To test if something is listening on port 3690, just open a DOS box in
Windows and enter
telnet ip-of-the-server 3690
if you then see some output and not an error message, then there's
something listening on that port.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Aug 31 21:04:20 2005