Jason Butlin wrote:
> We have a nightly process on one of our machines, which checkouts some
> source from SVN and builds all the projects. At the start of this
> process we rename the previously checked out source to another
> directory directory, purely as a precaution. However, I've noticed
> that lately this sometimes fails due to access denied.
Download the command-line tool "handle.exe" from sysinternals.com
<http://www.sysinternals.com/Utilities/Handle.html>, which lets you type
a full or partial path or file and it will return all processes which
are holding a lock on anything that matches. If the rename fails, have
it run "handle" and store the output.
But I'm curious about why you rename the previous checkout "purely as a
precaution". As a precaution against what? Do you think Subversion will
eat some of your files? You can always go back and checkout based on
revion number or timestamp.
> Is this a bug? (I guess not since the whole point of TSVNCache is to
> keep track of the files) Is there any way to tell TSVNCache to release
> it locks? Or even is it possible to not use TSVNCache on this machine
> at all (speed isn't really important on this machine)
Do you need TSVN at all on this machine, or are the command-line tools
sufficient?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jul 29 19:30:21 2005