summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-10-21 16:46:22 -0400
committerJoey Hess <joey@gnu.kitenet.net>2009-10-21 16:46:22 -0400
commit14526ef59772c0e1b60866b8149e478d82a4b70f (patch)
tree9e431ba00bac34d55ac737d5f3c3ec6198f868d2 /doc
parentb9071082717cd7fd56e66963b47a6d589848e062 (diff)
response
Diffstat (limited to 'doc')
-rw-r--r--doc/forum/Cannot_write_to_commitlock.mdwn9
1 files changed, 8 insertions, 1 deletions
diff --git a/doc/forum/Cannot_write_to_commitlock.mdwn b/doc/forum/Cannot_write_to_commitlock.mdwn
index a5d4bf440..81b0cdeb3 100644
--- a/doc/forum/Cannot_write_to_commitlock.mdwn
+++ b/doc/forum/Cannot_write_to_commitlock.mdwn
@@ -14,4 +14,11 @@ Now ~/ianbarton/.ikiwiki exists and is owned and writable by me. I have tried to
Ian.
-
+> I'm guessing that this is some kind of permissions problem,
+> and that the error message is just being misleading.
+>
+> When you push the changes to the server, what user is
+> git logging into the server as? If that user is different
+> than `ian` (possibly due to using git-daemon?), the post-commit
+> wrapper needs to be setuid to `ian`. This ensures that ikiwiki
+> runs as you and can see and write to the files. --[[Joey]]