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

Problems with exclusive-locking

From: bugreport <M8R-fj4tn21_at_thisisnotmyrealemail.com>
Date: Thu, 27 Feb 2014 01:04:41 -0800 (PST)

Hi folks,

I've just updated to TSVN 1.8.5 recently and the overall impression is very well.
One of the main reasons for upgrading from 1.7.x is the new exclusive-locking option the subversion 1.8 release notes write about. We are instructed to keep our working-copies on network storage (as building is only available on one special command-line-only machine) and I try to see if/what performance benefits we can see.

For enabling this in TSVN I've added the following part to the subversion config file (opened via TSVN settings dialogue):

# ----------------------------------------
### Section for configuring working copies.
[working-copy]
### Set to a list of the names of specific clients that should use
### exclusive SQLite locking of working copies. This increases the
### performance of the client but prevents concurrent access by
### other clients. Third-party clients may also support this
### option.
### Possible values:
### svn (the command line client)
# exclusive-locking-clients =
### Set to true to enable exclusive SQLite locking of working
### copies by all clients using the 1.8 APIs. Enabling this may
### cause some clients to fail to work properly. This does not have
### to be set for exclusive-locking-clients to work.
exclusive-locking = true
# ----------------------------------------

I've recognized that with exclusive-locking enabled the working copy is still locked (resulting in sqlite [S5] on command line) after TSVN->update *as long as the update dialogue is open* - **even if the update itself was long finished**.
I guess TSVN (or at least the code below the update dialogue) does not end/close the API.

Another issue (that would be good to solve first) can be seen if a working copy is locked: the context menu in Windows Explorer does not open at all (only for the locked working copy [and all files in all sub-folders]). Please try to have a "clean" timeout and maybe list something like TSVN (time-out) in context menu for not blocking the context menu.

The commit dialogue (if opened before and is refreshed during lock) reports "there is nothing to do for TSVN", something like "The working-copy is currently locked, please try again later." would be nice in this case.

BTW: Is there an possible entry for "exclusive-locking-clients" that works with TSVN? I've tried TortoiseProc, TortoiseProc.exe, TSVN, svn - none of them worked and I had to enable "exclusive-locking" to use it for TSVN.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3073693

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-02-27 10:04:45 CET

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