Canceled import causes MutexLocked error on subsequent import.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create repo
2. Add some files (1000)
3. Import another 2995 files. While scanning the work dir, Ctrl+C to abort.
4. Do it again.
5. See
C:\>boar import S:\xxx\years\2007 -W xxx/years/2007
Looking for files: 2995
Verifying checksum cache: 2995
Scanning: 0 files and 0 Mb remaining (100.0% complete, 5.0 Mb/s)
Loading session... done
Calculating changes... done
Traceback (most recent call last):
  File "boar", line 1340, in <module>
  File "boar", line 1248, in main
  File "boar", line 634, in cmd_import
  File "workdir.pyc", line 325, in checkin
  File "workdir.pyc", line 364, in __create_snapshot
  File "jsonrpc.pyc", line 651, in __call__
  File "jsonrpc.pyc", line 624, in __req
  File "jsonrpc.pyc", line 356, in loads_response
Exception: Unknown remote exception: {"message": "Mutex 'xxx' was already locked
. Lockfile is '/home/dacboar/boarrepo/tmp/mutex-744b41f0dccd32ebf5d525bc1c64af5a
'", "name": "MutexLocked", "module": "common"}
Boar is running on a hosted SSH account as the server, windows 8 as local 
client, jpgs mainly on local NAS drive.

version: boar-16-Nov-2012-setup-win32.exe

is there any workaround or way to reset? It takes awhile to blow up.

Original issue reported on code.google.com by david.ch...@gmail.com on 19 Dec 2013 at 2:28

[GoogleCodeExporter]

Duh. I believe the answer is 'rm -rf 
/home/dacboar/boarrepo/tmp/mutex-744b41f0dccd32ebf5d525bc1c64af5a' but it would 
be nice to reset it somehow without shell access.

Original comment by david.ch...@gmail.com on 19 Dec 2013 at 3:13