doc: Remove reference to NetRestrict wildcards

Commit 80fc888a9223050481de932233fe7121a48df194 got some of this, but
forgot the other reference. We don't support these anywhere, so remove
it here, too.

FIXES 125340

Reviewed-on: http://gerrit.openafs.org/7564
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Derrick Brashear <shadow@dementix.org>
(cherry picked from commit 4ae005062e2c927b77ea23d95934d5af463878b3)

Change-Id: I58e0fa2ea138a08b45d136abb9fcd43f9f3dc11a
Reviewed-on: http://gerrit.openafs.org/7670
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
Tested-by: Jeffrey Altman <jaltman@your-file-system.com>

diff --git a/doc/man-pages/pod5/NetRestrict.pod b/doc/man-pages/pod5/NetRestrict.pod
index e69b5792bd46b960de339aa0cbecbecd9ea1c160..42086da2fe26bc1768bc16bc846dd3ee1939bd13 100644 (file)
--- a/doc/man-pages/pod5/NetRestrict.pod
+++ b/doc/man-pages/pod5/NetRestrict.pod
@@ -28,10 +28,7 @@ list in kernel memory.
 
 The F<NetRestrict> file is in ASCII format. One IP address appears on each
 line, in dotted decimal format. The order of the addresses is not
-significant. The value C<255> is a wildcard that represents all possible
-addresses in that field. For example, the value C<192.12.105.255>
-indicates that the Cache Manager does not register any of the addresses in
-the C<192.12.105> subnet.
+significant.
 
 To display the addresses the Cache Manager is currently registering with
 File Servers, use the B<fs getclientaddrs> command.