Stefan Küng wrote:
> I've heard that plink has problems on multi-core processors. Are you
> now using such a machine with e.g. a dual-core processor?
Nope. A very modern Pentium-M, but not dual-core.
It got me thinking though, so I tried on a different box - a year-old,
slower, Pentium-M running WinXP Media Center, and that one worked fine.
Same version of TortoiseSVN and Putty. Hmmm....
>> I'm now at something of a loss as to how to investigate further. I'm
>> getting no errors, and no logs, on either the client or the server.
>> Just files that won't behave, and a machine that just jumps to 100%.
>>
>> Can anyone offer some suggestions?
>
> This seems to be a problem in plink (TortoisePlink is just a small
> hack to get rid of the DOS-box, no real change to plink is done
> there). So I can't really help you there, sorry.
Oh well.
I did manage to re-configure TortoiseSVN to run SSH through a script,
and then added some debugging calls to the script to log things. No
particular help. I tried this with both the TortoisePlink (0.57) and the
Putty plink (0.58).
I also added heaps of debugging on the server side, but not much help
there either.
But then I did manage to get a workaround....
The last thing I tried was to set up a permanent SSH tunnel from port
3690 on the Windows box through to port 3690 on the SVN server, and
access the repository through svn://localhost/path/to/repos. This worked
as far performing a checkout.
I still have to set up access rights correctly on the SVN server so that
the direct svnserve process lets me perform a commit, but it's
definitely an improvement so far...
Cheers,
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Tue Aug 22 22:08:32 2006