This is on NFS and with a large check in so it is worst case scenario but
still I'm seeing this error when people simultaneously do certain heavy
weight actions.
Are there any settings that would help here? I've dug though the docs and
not seen anything yet. I'll dig though the code tonight but pointers from
the experts would be appreciated.
FYI, I think these are probably unnecessary failures, however I grant that
is may be tough to differentiate from real issues such as db not readable.
I think fossil could possibly do a couple things here:
1. Interleave sync actions
2. On failure in sync tell the user that the db is probably busy and try
again in a few minutes.
[830] > fossil update
Autosync: file:///blah/blah.fossil
Bytes Cards Artifacts Deltas
Sent: 6945 146 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: 3842 bytes sent, 871 bytes received
fossil: Autosync failed
--------------
updated-to: 9012cff7d15010018d2fdd73375d198b27116844 2011-10-18 22:33:49
UTC
tags: trunk
comment: initial empty check-in (user: blah)
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
