[fossil-users] fixing "db locked" error

2015-02-05 Thread bch
On a remote machine, I was running "fossil co ", when the checkout stopped to ask if I wanted to overwrite a file, and simultaneously, my ssh session had hung. I killed that ssh session, re-logged into the remote. There is no stray ssh/login session I can see, nor old instance of fossil running. T

Re: [fossil-users] fixing "db locked" error

2015-02-05 Thread Richard Hipp
On 2/5/15, bch wrote: > On a remote machine, I was running "fossil co ", when the > checkout stopped to ask if I wanted to overwrite a file, and > simultaneously, my ssh session had hung. I killed that ssh session, > re-logged into the remote. There is no stray ssh/login session I can > see, nor

Re: [fossil-users] fixing "db locked" error

2015-02-05 Thread bch
Its even better -- the Remote Machine is a cluster of machines sharing disk. I solved the immediate problem -- however this raises a question: Is there a --ignore-advisory-locks switch to fossil, or can we (The List) have a discussion about this ? -bch On 2/5/15, Richard Hipp wrote: > On 2/5/1

Re: [fossil-users] fixing "db locked" error

2015-02-05 Thread Richard Hipp
On 2/5/15, bch wrote: > Its even better -- the Remote Machine is a cluster of machines sharing > disk. I solved the immediate problem -- however this raises a > question: > > Is there a --ignore-advisory-locks switch to fossil, or can we (The > List) have a discussion about this ? > The option is

Re: [fossil-users] fixing "db locked" error

2015-02-05 Thread bch
Understood -- I hope I never see an need to run this -- I'd look long, and hard before I did. In case anybody is perceiving my interest in subverting POSIX locking as implied embracing of subverting POSIX locking: I'm am not condoning this. -bch On 2/5/15, Richard Hipp wrote: > On 2/5/15, bch

Re: [fossil-users] fixing "db locked" error

2015-02-05 Thread Ron W
On Thu, Feb 5, 2015 at 3:25 PM, bch wrote: > Understood -- I hope I never see an need to run this -- I'd look long, > and hard before I did. In case anybody is perceiving my interest in > subverting POSIX locking as implied embracing of subverting POSIX > locking: I'm am not condoning this. > Wh

Re: [fossil-users] fixing "db locked" error

2015-02-05 Thread Matt Welland
If an sqlite3 db gets locked on NFS the "fix" is to copy the file to a tmp dir and copy dump it: mkdir tmp cp foo.fossil* tmp rm foo.fossil* sqlite3 tmp/foo.fossil .dump | sqlite3 foo.fossil This deals gracefully with cases where there is a .journal file, locks and other problems. Just my $0.02