Fossil SCM
sync.wiki: update the default value for the lock timeout period, [forum:242a02121f|per forum post 242a02121f].
Commit
62572ab606345d98d788156c79fc7e80b79739b8e91716d2873491c7b1deaf1d
Parent
c0714a05ec1a52c…
1 file changed
+1
-1
+1
-1
| --- www/sync.wiki | ||
| +++ www/sync.wiki | ||
| @@ -718,11 +718,11 @@ | ||
| 718 | 718 | If some other client has already indicated that it was also |
| 719 | 719 | trying to commit against CHECKIN-HASH, that indicates that a |
| 720 | 720 | fork is about to occur, and the server will reply with |
| 721 | 721 | a "ci-lock-fail" pragma (see below). Check-in locks |
| 722 | 722 | automatically expire when the check-in actually occurs, or |
| 723 | -after a timeout (currently 24-hours but subject to change). | |
| 723 | +after a timeout (currently one minute but subject to change). | |
| 724 | 724 | |
| 725 | 725 | <li><p><b>ci-lock-fail</b> <i>LOGIN MTIME</i></p> |
| 726 | 726 | <p>When a server receives two or more "ci-lock" pragma messages |
| 727 | 727 | for the same check-in but from different clients, the second a |
| 728 | 728 | subsequent ci-lock will provoke a ci-lock-fail pragma in the |
| 729 | 729 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -718,11 +718,11 @@ | |
| 718 | If some other client has already indicated that it was also |
| 719 | trying to commit against CHECKIN-HASH, that indicates that a |
| 720 | fork is about to occur, and the server will reply with |
| 721 | a "ci-lock-fail" pragma (see below). Check-in locks |
| 722 | automatically expire when the check-in actually occurs, or |
| 723 | after a timeout (currently 24-hours but subject to change). |
| 724 | |
| 725 | <li><p><b>ci-lock-fail</b> <i>LOGIN MTIME</i></p> |
| 726 | <p>When a server receives two or more "ci-lock" pragma messages |
| 727 | for the same check-in but from different clients, the second a |
| 728 | subsequent ci-lock will provoke a ci-lock-fail pragma in the |
| 729 |
| --- www/sync.wiki | |
| +++ www/sync.wiki | |
| @@ -718,11 +718,11 @@ | |
| 718 | If some other client has already indicated that it was also |
| 719 | trying to commit against CHECKIN-HASH, that indicates that a |
| 720 | fork is about to occur, and the server will reply with |
| 721 | a "ci-lock-fail" pragma (see below). Check-in locks |
| 722 | automatically expire when the check-in actually occurs, or |
| 723 | after a timeout (currently one minute but subject to change). |
| 724 | |
| 725 | <li><p><b>ci-lock-fail</b> <i>LOGIN MTIME</i></p> |
| 726 | <p>When a server receives two or more "ci-lock" pragma messages |
| 727 | for the same check-in but from different clients, the second a |
| 728 | subsequent ci-lock will provoke a ci-lock-fail pragma in the |
| 729 |