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 <[email protected]> wrote: > On 2/5/15, bch <[email protected]> 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 ? >> > > SQLite uses Posix Advisory Locking. The locks should clear > automatically when the process dies. > > Possible things that can go wrong: (1) You are using NFS where file > locking is broken. (2) You have set "dot-file" locking for your > system and there is a stray dot-file remaining behind. (3) The > process that you think is now dead is really a zombie and is still > holding onto the locks. > > -- > D. Richard Hipp > [email protected] > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
