aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-08-04 16:27:28 -0400
committerJoey Hess <joey@gnu.kitenet.net>2009-08-04 16:27:28 -0400
commita41d8177d4769daf20ea88baddedcc3cbcd56c21 (patch)
treed7714522518e4b60bff842c44b5f2a91afc8da2b /doc
parent3f33d3979c89610e1c8514c71c887acfa1c3ccac (diff)
downloadikiwiki-a41d8177d4769daf20ea88baddedcc3cbcd56c21.tar
ikiwiki-a41d8177d4769daf20ea88baddedcc3cbcd56c21.tar.gz
response
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/post-commit_hangs.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/post-commit_hangs.mdwn b/doc/bugs/post-commit_hangs.mdwn
index c28a34040..a19441b92 100644
--- a/doc/bugs/post-commit_hangs.mdwn
+++ b/doc/bugs/post-commit_hangs.mdwn
@@ -10,6 +10,16 @@ I installed ikiwiki v3.14159 in /usr/local from tarball (/usr contains an older
>> Hmm, maybe it's the recursive call to ikiwiki which is the problem.
>> The underlying VCS is mercurial. --Ali
+>>> You're not supposed to run ikiwiki -setup manually in your post commit hook.
+>>> Doing so will certianly lead to a locking problem; it also forces ikiwiki to rebuild
+>>> the entire wiki anytime a single page changes, which is very inefficient!
+>>>
+>>> Instead, you should use the `mercurial_wrapper` setting
+>>> in the setup file, which will make ikiwiki generate a small
+>>> executable expressly designed to be run at post commit time.
+>>> Or, you can use the `--post-commit` option, as documented
+>>> in [[rcs/mecurial]] --[[Joey]]
+
> Also, how have you arranged to keep it from seeing the installation in /usr? Perl could well be loading
> modules from the old installation, and if it's one with a different locking strategy that would explain your problem. --[[Joey]]