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 from extensively using sqlite3 on NFS (not just fossil stuff). On Thu, Feb 5, 2015 at 12:49 PM, bch <brad.har...@gmail.com> wrote: > On a remote machine, I was running "fossil co <branch>", 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. Trying to re-run the > checkout, however, informs me that the DB is locked. What's the best > fix ? > > > -bch > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
