[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Erratic Locking Behavior With TortoiseSVN

From: Larry Walker <larryw_at_voicebox.com>
Date: 2005-11-21 22:28:14 CET

I've investigated Stefan's suggestions:
1. Virus Scanner - I turned off the "Symantec Norton AntiVirus 2004" Auto-Protect mode. I left the nightly scan on, which sometimes temporarily and inconsistently fixes the problem. It is very unclear if the virus scanner causes the problem, the age of the working area seems to be a major factor. I installed TortoiseSVN on a test box that had neither a virus scanner or Cygwin and everything has worked fine for several days.
2. Cygwin - I ran tests without starting Cygwin (after a reboot) and tests without running the Cygwin svn client. There were no new occurrences of the problem. In fact, the best fix to date is to do a Cygwin "chmod +w filename", this seems to permanently make files properly switch between the read-only and writable states when locking and unlocking. Microsoft's SFU (Services For UNIX) chmod also fixes the files

Other Observations:
* The panacea of rebooting windows doesn't help.
* The problem doesn't appear to be due to the repository - the same set of files were checked out twice to different working areas, one area works, the other fails.
* With TortoiseSVN-, I observed large %CPU (30-40%) from TSVNCache.exe much after it was last used; I reinstalled 1.2.6 and saw much lower numbers.
* I get different errors on Wordpad save attempts:
Locked but no write permissions - "Access to .../file was denied"
Unlocked and no write permissions - "Save As" Window with a .txt default
* The locking comment is now fully functional with the Apache server, the TortoiseSVN help file Section 5.18.2 needs updating.

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn@gmail.com]
Sent: Wednesday, November 16, 2005 9:34 AM
To: users@tortoisesvn.tigris.org
Subject: Re: Erratic Locking Behavior With TortoiseSVN

Larry Walker wrote:

> I've run into some strange locking behavior with TortoiseSVN. Server:
> Linux with Subversion 1.2.3 and Apache 2.0.54, Client: WinXP SP2. The
> test files have the needs-lock property set. When locking a file with
> TortoiseSVN, the icon shows the lock and the windows property changes
> from read-only to "writable", but the file changes can't be saved -

If the overlay changes, then that means that the "readonly" flag has
been removed. If the file is still not writable, then that would mean
some other program has the file open (virus scanner are known to behave
badly here), or that you don't have the right to write to that file
(NTFS permissions are different from the readonly flag).

> error: "Access to .../file was denied". Cygwin shows the file is still
> read-only. Doing the same lock/write/commit operations works properly
> from the Cygwin command line. Changing the file to writable with Cygwin
> and doing the rest with TortoiseSVN also works. This strange behavior
> doesn't occur with a fresh working copy but only after an area has been
> used for a while (sorry there is no better definition of when things go
> bad).

Maybe it's some interference with you using the cygwin svn client
together with TSVN. If you're working on windows, you should use the
windows SVN command line client. Or only the cygwin client and no other
Subversion clients.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Mon Nov 21 21:38:14 2005

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.