man1-editing-pass-20051209

[openafs.git] / doc / man-pages / pod1 / fs_flushmount.pod

diff --git a/doc/man-pages/pod1/fs_flushmount.pod b/doc/man-pages/pod1/fs_flushmount.pod
index fdc2854..2132127 100644 (file)
--- a/doc/man-pages/pod1/fs_flushmount.pod
+++ b/doc/man-pages/pod1/fs_flushmount.pod
@@ -4,59 +4,59 @@ fs flushmount - Forces the Cache Manager to discard a mount point
 
 =head1 SYNOPSIS
 
-B<fs flushmount> [B<-path> <I<dir/file path>>+]  [-help]
+B<fs flushmount> [B<-path> <I<dir/file path>>+] [B<-help>]
 
-B<fs flushm> [B<-p> <I<dir/file path>>+]  [-h]
+B<fs flushm> [B<-p> <I<dir/file path>>+] [B<-h>]
 
 =head1 DESCRIPTION
 
-The fs flushmount command removes from the cache all information
-associated with each mount point named by the B<-path>
-argument. The next time an application accesses the mount point, the
-Cache Manager fetches the most current version of it from the File
-Server. Data cached from the associated volume is not affected.
+The B<fs flushmount> command removes from the cache all information
+associated with each mount point named by the B<-path> argument. The next
+time an application accesses the mount point, the Cache Manager fetches
+the most current version of it from the File Server. Data cached from the
+associated volume is not affected.
 
-The command's intended use is to discard information about mount
-points that has become corrupted in the cache. (The Cache Manager
-periodically refreshes cached mount points, but the only other way to discard
-them immediately is to reinitialize the Cache Manager by rebooting the
-machine.) Symptoms of a corrupted mount point included garbled output
-from the B<fs lsmount> command, and failed attempts to change
-directory to or list the contents of a mount point.
+The command's intended use is to discard information about mount points
+that has become corrupted in the cache. (The Cache Manager periodically
+refreshes cached mount points, but the only other way to discard them
+immediately is to reinitialize the Cache Manager by rebooting the
+machine.) Symptoms of a corrupted mount point included garbled output from
+the B<fs lsmount> command, and failed attempts to change directory to or
+list the contents of a mount point.
 
-To flush cached data rather than a mount point, use the fs flush
-or B<fs flushvolume> command.
+To flush cached data rather than a mount point, use the B<fs flush> or
+B<fs flushvolume> command.
 
 =head1 OPTIONS
 
 =over 4
 
-=item -path
+=item B<-path> <I<dir/file path>>+
 
-Names each mount point to flush from the cache. Partial pathnames
-are interpreted relative to the current working directory, which is also the
+Names each mount point to flush from the cache. Partial pathnames are
+interpreted relative to the current working directory, which is also the
 default value if this argument is omitted.
 
-=item -help
+=item B<-help>
 
-Prints the online help for this command. All other valid options
-are ignored.
+Prints the online help for this command. All other valid options are
+ignored.
 
 =back
 
 =head1 EXAMPLES
 
 The following command flushes from the cache the mount point for user
-B<pat>'s home directory:
+C<pat>'s home directory:
 
    % fs flushm /afs/abc.com/usr/pat
 
 =head1 PRIVILEGE REQUIRED
 
-The issuer must have the B<l> (lookup) permission on the
-ACL of the root directory of the volume that houses the file or directory
-named by the B<-path> argument, and on the ACL of each directory that
-precedes it in the pathname.
+The issuer must have the C<l> (lookup) permission on the ACL of the root
+directory of the volume that houses the file or directory named by the
+B<-path> argument, and on the ACL of each directory that precedes it in
+the pathname.
 
 =head1 SEE ALSO