From: Derrick Brashear <shadow@dementia.org>
Date: Wed, 28 Apr 2010 03:48:36 +0000 (-0400)
Subject: no fs sa /afs in dynroot mode
X-Git-Tag: openafs-devel-1_5_75~93
X-Git-Url: https://git.openafs.org/?p=openafs.git;a=commitdiff_plain;h=20bf8feacddea0000578bacf5789e288d99596c5

no fs sa /afs in dynroot mode

change the quick start guide so people stop asking why they can't
set the ACL on /afs.

Change-Id: Iffc6c95564e99c01cef1b2b54d6b35e9bd01f38c
Reviewed-on: http://gerrit.openafs.org/1872
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Derrick Brashear <shadow@dementia.org>
---

diff --git a/doc/xml/QuickStartUnix/auqbg005.xml b/doc/xml/QuickStartUnix/auqbg005.xml
index 418e917..95f5a74 100644
--- a/doc/xml/QuickStartUnix/auqbg005.xml
+++ b/doc/xml/QuickStartUnix/auqbg005.xml
@@ -5402,6 +5402,14 @@ and so may already be available at your site.</para>
           role="bold">system:administrators</emphasis> group. It is a default entry that AFS places on every new volume's root
           directory.</para>
 
+	  <para>The top-level AFS directory, typically /afs, is a special case:
+	    when the client is configured to run in dynroot mode (e.g. 
+	    <emphasis role="bold">afsd -dynroot</emphasis>, attempts to set
+	    the ACL on this directory will return <emphasis role="bold">
+	      Connection timed out</emphasis>. This is because the dynamically-
+	    generated root directory is not a part of the global AFS space,
+	    and cannot have an access control list set on it.</para>
+
           <programlisting>
    # <emphasis role="bold">/usr/afs/bin/fs setacl /afs system:anyuser rl</emphasis>
 </programlisting>