deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Added information about install destinations supported by SELinux to troubleshooting guide

Browse source
This commit is contained in:
Frode Rystad 2012-06-20 08:59:42 +02:00
parent c9d5a13194
commit 858f13cf31
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
doc/extras/sts.mkd
View file

@ -321,6 +321,13 @@ This is a quick checklist:
* Some OSs/distributions require that the "git" user should have a password * Some OSs/distributions require that the "git" user should have a password
and/or not be a locked account. You may want to check that as well. and/or not be a locked account. You may want to check that as well.
* If your server is running SELinux, and you install gitolite to
`/var/gitolite` or another location unsupported by default SELinux
policies, then SELinux will prevent sshd from reading
`.ssh/authorized_keys`. Consider installing gitolite to
`/var/lib/gitolite`, which is a supported location by default SELinux
policies.
* If all that fails, log onto the server as root, `cd /var/log`, and look * If all that fails, log onto the server as root, `cd /var/log`, and look
for a file called `auth.log` or `secure` or some such name. Look inside for a file called `auth.log` or `secure` or some such name. Look inside
this file for messages matching the approximate time of your last attempt this file for messages matching the approximate time of your last attempt