You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Satoshi Nakamura <sn...@zak.att.ne.jp> on 2003/06/07 18:37:56 UTC
svn cannot run with cygwin-sshd
Hi,
I encountered a problem when I run svn with cygwin-sshd. I use svn-0.23.0
on Windows 2000. I installed cygwin-sshd as a service and tried using
svnserve over ssh.
When I tried to use svnserve over ssh, I got an error:
> $ svn co svn+ssh://localhost/repos
> svn: Network connection closed unexpectedly
> svn: Connection closed unexpectedly
So I tried running svnserve over ssh directly, and got an error:
> $ ssh localhost svnserve -t
> svn: error: cannot set console input codepage (code 6)
It seems that calling SetConsoleCP caused this error because there is no
console bound to the process running in sshd.
I changed the source code (subversion/libsvn_subr/cmdline.c) not to call
SetConsoleCP and built it, then it worked fine.
--
Satoshi Nakamura <sn...@zak.att.ne.jp>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svn cannot run with cygwin-sshd
Posted by Branko Čibej <br...@xbc.nu>.
Satoshi Nakamura wrote:
>Hi,
>
>I encountered a problem when I run svn with cygwin-sshd. I use svn-0.23.0
>on Windows 2000. I installed cygwin-sshd as a service and tried using
>svnserve over ssh.
>
>When I tried to use svnserve over ssh, I got an error:
>
>
>>$ svn co svn+ssh://localhost/repos
>>svn: Network connection closed unexpectedly
>>svn: Connection closed unexpectedly
>>
>>
>
>So I tried running svnserve over ssh directly, and got an error:
>
>
>>$ ssh localhost svnserve -t
>>svn: error: cannot set console input codepage (code 6)
>>
>>
>
>It seems that calling SetConsoleCP caused this error because there is no
>console bound to the process running in sshd.
>
>I changed the source code (subversion/libsvn_subr/cmdline.c) not to call
>SetConsoleCP and built it, then it worked fine.
>
>
Yes, this is a known problem, see
http://subversion.tigris.org/issues/show_bug.cgi?id=872
especially the last two comments. Unfortunately, just removing the
SetConsoleCP is a bad idea in general, because then the cmdline client
won't read and write to the console correctly.
--
Brane Čibej <br...@xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org