bugs.
You can test your new POD documentation by running the check-pod script
- in this directory. (And check other people's documentation and find any
- problems that have crept in.)
+ in this directory with "prove check-pod". (And check other people's
+ documentation and find any problems that have crept in.) You will need
+ to have Test::Pod installed.
Known Problems
#!/usr/bin/perl
#
-# Written by Jason Edgecombe based on the Test::Pod documentation. Run
-# it to syntax-check all of the POD files.
+# Written by Jason Edgecombe based on the Test::Pod documentation. The
+# best way to run it is to run:
+#
+# prove check-pod
+#
+# from the doc/man-pages directory, which will show any errors found in
+# any of the POD files.
use strict;
use Test::More;
=for html
<div class="synopsis">
-B<vos changeloc> S<<< B<-server> <I<new server name>> >>>
- S<<< B<-partition> <I<new partition location>> >>>
- S<<< B<-id> <I<volume name or ID>> >>>
+B<vos changeloc> S<<< [B<-server>] <I<new server name>> >>>
+ S<<< [B<-partition>] <I<new partition location>> >>>
+ S<<< [B<-id>] <I<volume name or ID>> >>>
S<<< [B<-cell> <I<cell name>>] >>> [B<-noauth>] [B<-localauth>]
[B<-verbose>] [B<-encrypt>] [B<-help>]
-B<vos changel> S<<< B<-s> <I<new server name>> >>>
- S<<< B<-p> <I<new partition location>> >>>
- S<<< B<-i> <I<volume name or ID>> >>>
+B<vos changel> S<<< [B<-s>] <I<new server name>> >>>
+ S<<< [B<-p>] <I<new partition location>> >>>
+ S<<< [B<-i>] <I<volume name or ID>> >>>
S<<< [B<-c> <I<cell name>>] >>> [B<-n>] [B<-l>] [B<-v>] [B<-e>] [B<-h>]
=for html