On Mon, Aug 08, 2011 at 03:36:29PM -0400, Martin S. Weber wrote: > On 08/06/11 12:47, Kevin Quick wrote: > > $ fossil sync PATH-TO-REPO > > Bytes Cards Artifacts Deltas > > Sent: 3897 82 0 0 > > Error: Database error: database is locked > > DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private) > > Received: 118 1 0 0 > > Total network traffic: 2225 bytes sent, 813 bytes received > > $ > > > > This happens every time. I found the suggestion for "PRAGMA > > journal_mode=WAL;" in sqlite mode, but that had no effect. > > So I think it's an issue with having file:/// level access open to a fossil > repository multiple times / from multiple fossil instances? I'm just fishing > the muddy waters here, but it's pretty obvious how to force the "Database > error: database is locked" to appear to me.
I have fossil repositories opened in multiple directories each, and I only hit "database locked" troubles if I'm really running at the same time two fossil operations on the same repository. So, I don't understand what happens in your situation. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
