On 4/8/06, Robert William Vesterman <bob@vesterman.com> wrote:
> I am currently running the conversion utility vss2svn, found at
> http://vss2svn.tigris.org, to migrate from an existing VSS repository to
> a new Subversion repository. I had read that it's slow, but I guess I
> was unprepared for how slow. It's been going for over four hours now,
> and it hasn't yet produced any feedback (either to stdout or to stderr).
>
> So, I am growing concerned that it might not be doing anything.
>
> Is this normal? Running for over four hours, with no feedback? This is
> on a VSS project that doesn't seem terribly large to me.
How large a repository? Did you do a test run with a small repository
first, to get a feel for how it works?
> Also, I had read that VSS is very slow over the network, so I made sure
> to do this migration locally on the machine with the VSS repository, and
> set SSDIR to a local path rather than a network path. However, I am
> concerned that I might not have done so sufficiently for vss2svn's needs:
>
> I opened up a DOS window, and did a "set SSDIR=c:\blah", and then ran
> vss2svn from that same DOS window.
>
> However, the machine's "regular" environment variables have SSDIR set to
> "\\machine\blah", which is the network path to c:\blah on the same
> machine. Is it possible that vss2svn is getting SSDIR from there,
> rather than from the DOS window I'm running it in?
You can check the current environment by typing "set" at the command
prompt and it will respond with all the environment variables you have
in that shell.
Unless you're using Win9x, you are not using DOS, you are using a
command shell which accepts most of the same commands and runs most of
the same programs, but is quite different from DOS.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Apr 9 14:11:55 2006