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

(minor) doc the effect of openssh 5.6 more clearly

Browse source
This commit is contained in:
Sitaram Chamarty 2011-02-06 06:23:37 +05:30
parent df157e72b5
commit 9b212ed0ef
1 changed files with 19 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
doc/report-output.mkd
View file

@ -13,6 +13,7 @@ In this document:
* <a href="#_the_info_command">the "info" command</a>
* <a href="#_interpreting_the_output">interpreting the output</a>
* <a href="#_using_patterns_to_limit_output">using patterns to limit output</a>
* <a href="#_side_note_openssh_5_6">side note: openssh 5.6</a>
* <a href="#_the_expand_command">the "expand" command</a>
----
@ -103,6 +104,24 @@ The pattern is also mandatory when an admin wants to find out what access some
*other* user has, which you may have guessed from the syntax in the "usage"
line above.
<a name="_side_note_openssh_5_6"></a>
#### side note: openssh 5.6
It used to be that the gitolite documentation would say "just use `ssh
git@server`" in the past, because gitolite defaults to the "info" command if
no command is passed.
However, starting with [openssh 5.6][openssh56], this won't work. Openssh
will now "Kill channel when pty allocation requests fail". This means that
gitolite is not even invoked; you only get a message about pty allocation
failure, followed by "connection closed".
So now you have to use an explicit "info" command, (`ssh git@server info`) or
add the `-T` option to ssh (`ssh -T git@server`).
[openssh56]: http://www.openssh.org/txt/release-5.6
<a name="_the_expand_command"></a>
### the "expand" command