search

janestreet / jenga

Build system
90 stars 12 forks source link

jenga locks itself out when files are on shared folder in a VM #9

Open agarwal opened 9 years ago

agarwal commented 9 years ago

Using a VirtualBox VM, if my code directory is a shared folder, i.e. a mount back to the host's filesystem, I get this:

$ jenga
*** jenga: [12135] root=/host/Desktop/tmp/jenga-test, sys=Linux, j=1, f=1
*** jenga: ERROR: jenga already running, lockfile = /host/Desktop/tmp/jenga-test/.jenga.lock.nfs_lock
*** jenga: Quit; exit_code = 5

There is no other jenga process running. This call itself creates the lock file and locks itself out.

Nick-Chapman commented 9 years ago

Have you tried removing the lock files (.jenga.lock*) by hand?

On 14 November 2014 19:00, Ashish Agarwal notifications@github.com wrote:

Using a VirtualBox VM, if my code directory is a shared folder, i.e. a mount back to the host's filesystem, I get this:

$ jenga * jenga: [12135] root=/host/Desktop/tmp/jenga-test, sys=Linux, j=1, f=1 * jenga: ERROR: jenga already running, lockfile = /host/Desktop/tmp/jenga-test/.jenga.lock.nfs_lock *\ jenga: Quit; exit_code = 5

There is no other jenga process running. This call itself creates the lock file and locks itself out.

Reply to this email directly or view it on GitHub https://github.com/janestreet/jenga/issues/9.

Nick Chapman nic@amadido.co.uk Beira Cottage, The Phygtle, Chalfont St. Peter, Bucks, SL9 0JT, UK. +44 1494 876885 (home) +44 7779 121533 (mobile)

agarwal commented 9 years ago

Yes, but it gets recreated.