[ARVADOS] updated: 2.1.0-792-g6fa1fbd93

[Git user]

Summary of changes:
 doc/install/container-shell-access.html.textile.liquid        | 2 +-
 doc/user/debugging/container-shell-access.html.textile.liquid | 7 ++++---
 2 files changed, 5 insertions(+), 4 deletions(-)

       via  6fa1fbd935fd665494ea87716aef901144d14479 (commit)
      from  3751d9e286c214dbe8c0cf078b4919c94a7c3407 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.


commit 6fa1fbd935fd665494ea87716aef901144d14479
Author: Ward Vandewege <ward at curii.com>
Date:   Mon May 17 11:25:29 2021 -0400

    17668: A few more tweaks after review feedback.
    
    Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <ward at curii.com>

diff --git a/doc/install/container-shell-access.html.textile.liquid b/doc/install/container-shell-access.html.textile.liquid
index 46aa4e382..e011a1c4d 100644
--- a/doc/install/container-shell-access.html.textile.liquid
+++ b/doc/install/container-shell-access.html.textile.liquid
@@ -39,6 +39,6 @@ The relevant configuration section is
 
 To enable the feature a firewall change may also be required. Traffic from the machine that runs @arvados-controller@ to the compute nodes in the port range above 1024 must be allowed.
 
-After changing the configuration, @arvados-controller@ must be restarted for the change to take effect. When enabling, the change will only affect containers started from that point on. When disabling, access is removed immediately for any running containers, as well as any containers started subsequently.
+After changing the configuration, @arvados-controller@ must be restarted for the change to take effect. When enabling, shell access will be enabled for any running containers. When disabling, access is removed immediately for any running containers, as well as any containers started subsequently. Restarting @arvados-controller@ will kill any active connections.
 
 Usage instructions for this feature are available in the "User guide":{{site.baseurl}}/user/debugging/container-shell-access.html.
diff --git a/doc/user/debugging/container-shell-access.html.textile.liquid b/doc/user/debugging/container-shell-access.html.textile.liquid
index a352b33b5..c17c2a89a 100644
--- a/doc/user/debugging/container-shell-access.html.textile.liquid
+++ b/doc/user/debugging/container-shell-access.html.textile.liquid
@@ -19,7 +19,7 @@ The @arvados-client@ program can be used to connect to a container in a running
 
 h2(#syntax). Syntax
 
-The @arvados-client shell@ tool has a number of command line arguments:
+The @arvados-client shell@ tool has the following syntax:
 
 <notextile>
 <pre><code>~$ <span class="userinput">arvados-client shell -h</span>
@@ -34,6 +34,8 @@ Options:
 </code></pre>
 </notextile>
 
+The @arvados-client shell@ command calls the ssh binary on your system to make the connection. Everything after _[username@]container-uuid_ is passed through to your OpenSSH client. This means many other SSH features can be used, e.g. -g, -f -N, -n, ...
+
 h2(#Examples). Examples
 
 Connect to a running container, using the container request UUID:
@@ -63,8 +65,7 @@ root at 0f13dcd755fa:~# nc -l -p 80
 And then, connecting to port 8888 locally:
 
 <notextile>
-<pre><code>~$ <span class="userinput">nc localhost 8888</span>
-hello
+<pre><code>~$ <span class="userinput">echo hello | nc localhost 8888</span>
 </code></pre>
 </notextile>
 

-----------------------------------------------------------------------


hooks/post-receive
--