From 4ae005062e2c927b77ea23d95934d5af463878b3 Mon Sep 17 00:00:00 2001 From: Andrew Deason Date: Mon, 18 Jun 2012 15:02:09 -0500 Subject: [PATCH] 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 Change-Id: I536336634beb835c9e1c93e23f8d7329fa821c96 Reviewed-on: http://gerrit.openafs.org/7564 Tested-by: BuildBot Reviewed-by: Derrick Brashear --- doc/man-pages/pod5/NetRestrict.pod | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/doc/man-pages/pod5/NetRestrict.pod b/doc/man-pages/pod5/NetRestrict.pod index e69b5792bd..42086da2fe 100644 --- a/doc/man-pages/pod5/NetRestrict.pod +++ b/doc/man-pages/pod5/NetRestrict.pod @@ -28,10 +28,7 @@ list in kernel memory. The F 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 command.