INN commit: trunk/doc/pod (readers.conf.pod)

[INN Commit]

    Date: Saturday, March 21, 2015 @ 06:30:37
  Author: iulius
Revision: 9798

readers.conf:  improve the first example to disambiguate its effect against local connections

Modified:
  trunk/doc/pod/readers.conf.pod

------------------+
 readers.conf.pod |   16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

Modified: readers.conf.pod
===================================================================
--- readers.conf.pod	2015-03-18 20:47:11 UTC (rev 9797)
+++ readers.conf.pod	2015-03-21 13:30:37 UTC (rev 9798)
@@ -628,18 +628,24 @@
 
     auth example.com {
         hosts: "*.example.com, example.com"
-        default: <LOCAL>
+        default: "<EXAMPLE>"
     }
 
     access full {
+        users: "<EXAMPLE>"
         newsgroups: *
     }
 
-Note that the access realm has no users: key and therefore applies to any
-user identity.  The only available auth realm only matches hosts in the
-"example.com" domain, though, so any connections from other hosts will be
-rejected immediately.
+Note that the above access realm could also be written without the
+users: key, in which case it applies to any user identity (though in
+this example, the user identity that will be assigned to all matching
+connections is C<< <EXAMPLE> >>).  It is however recommended to keep
+an explicit users: key so as to better view to whom the access block
+applies.
 
+As the only available auth realm only matches hosts in the "example.com"
+domain, any connections from other hosts will be rejected immediately.
+
 If you have some systems that should only have read-only access to the
 server, you can modify the example above slightly by adding an additional
 auth and access group: