When I am doing svn cleanup before every svn update I am not facing any
issues. But it would be great if I could figure out why it is causing
problems when I don't run svn cleanup.
On Mon, Oct 13, 2008 at 11:15 PM, vinay i <vinay.indresh_at_gmail.com> wrote:
> We are using Solaris i386 platform. We have a NFS mounted system. We are
> not using windows. How to tackle the problem? I am seeing this error quite
> On Mon, Oct 13, 2008 at 8:34 PM, David Weintraub <qazwart_at_gmail.com>wrote:
>> What platform are you on? If you're on Windows, are you using the
>> cygwin client or the native client? Are you using a shared network
>> drive as your working directory on Windows?
>> There are certain problems with the cygwin client that occur when
>> you're on a network drive or using some virus scanners that seem to
>> mess up the working directory. It can also happen with the regular
>> native Windows client and a shared drive too. See
>> <http://subversion.tigris.org/faq.html#wedged-wc> for more details why
>> this might happen.
>> The problem is not that the client is getting corrupted as much as a
>> second process attempted to read the files on the working directory
>> while the Subversion client was reading them too. Sometimes, it is the
>> result of killing the Subversion client in such a way when it is
>> processing that it doesn't have a chance to clean itself up. Again,
>> mainly on the Windows client.
>> David Weintraub
>> On Mon, Oct 13, 2008 at 10:47 AM, vinay i <vinay.indresh_at_gmail.com>
>> > Hi
>> > I am getting the svn lock issue very often. Is there any fine tuning
>> > required? When I try to do a svn update on a large tree I am facing this
>> > issue. Below is the error message
>> > svn: Working copy 'src/lib' locked
>> > svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
>> > Thanks
>> > Vinay
Received on 2008-10-14 17:52:43 CEST