2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-07-21 20:01:11 +00:00

man 1 manpage spelling corrections (batch 1)

This commit is contained in:
besawn
2022-02-01 17:40:43 -05:00
parent 9eae0941de
commit 9bff60368c
12 changed files with 13 additions and 13 deletions

View File

@@ -1,6 +1,6 @@
=head1 NAME
B<addkit> - Adds product software Kits to an xCAT cluster environmnet.
B<addkit> - Adds product software Kits to an xCAT cluster environment.
=head1 SYNOPSIS

View File

@@ -74,7 +74,7 @@ A comma-delimited list of valid full kit component names or kit component basena
addkitcomp -a -i rhels6.2-ppc64-netboot-compute comp-test2-1.0-1-rhels-6.2-ppc64
3. To add a kit component to osimage with incompatable osarch, osversion or ostype, use the -f (force) option:
3. To add a kit component to osimage with incompatible osarch, osversion or ostype, use the -f (force) option:
addkitcomp -f -i rhels6.2-ppc64-netboot-compute comp-test1-1.0-1-rhels-6.2-ppc64

View File

@@ -118,7 +118,7 @@ B<IP> - The IP address for the interface.
B<netmask> - The network mask for the interface.
B<gateway> - The gateay for the interface. This field only can be set when
B<gateway> - The gateway for the interface. This field only can be set when
the interface is added to 'rhevm' network.
=back

View File

@@ -332,7 +332,7 @@ Add a zFCP device to a device pool defined in xCAT. The device must have been
carved up in the storage controller and configured with a WWPN/LUN before it can
be added to the xCAT storage pool. z/VM does not have the ability to communicate
directly with the storage controller to carve up disks dynamically. xCAT will
find the a zFCP device in the specified pool that meets the size required, if
find a zFCP device in the specified pool that meets the size required, if
the WWPN and LUN are not given. The device address can be automatically assigned
by specifying 'auto'. The WWPN/LUN can be set as the LOADDEV in the directory
entry if (1) is specified as the 'loaddev'.

View File

@@ -88,7 +88,7 @@ Verbose output.
=head1 RETRUN VALUE
0 The command completed sucessfully.
0 The command completed successfully.
1 An error has occurred.

View File

@@ -45,7 +45,7 @@ For statelite:
where x is the name of the profile.
Any files specified by the B<-e> flag will also be exported. If B<-p> flag is specified, the names of the postscripts and the postbootscripts for the given node will be exported. The postscripts themselves need to be manualy exported using B<-e> flag.
Any files specified by the B<-e> flag will also be exported. If B<-p> flag is specified, the names of the postscripts and the postbootscripts for the given node will be exported. The postscripts themselves need to be manually exported using B<-e> flag.
For statelite, the litefile table settings for the image will also be exported. The litetree and statelite tables are not exported.

View File

@@ -28,7 +28,7 @@ Input to the command can specify any number or combination of the input options.
=item B<-F|--framework> I<kit_path_name>
Use this option to display the framework values of the specified Kit tarfile. This information is retreived directly from the tarfile and can be done before the Kit has been defined in the xCAT database. This option cannot be combined with other options.
Use this option to display the framework values of the specified Kit tarfile. This information is retrieved directly from the tarfile and can be done before the Kit has been defined in the xCAT database. This option cannot be combined with other options.
=item B<-K|--kitattr> I<kitattr_names>

View File

@@ -38,7 +38,7 @@ To setup NTP on the compute node, add I<setupntp> postscript to the I<postscript
=item B<-a|--all>
Setup NTP servers for both management node and the service node. If management node has SLES installed and used as I<ntpservers>, it is recommanded to use the I<setupntp> postscript to set up NTP server for service nodes.
Setup NTP servers for both management node and the service node. If management node has SLES installed and used as I<ntpservers>, it is recommended to use the I<setupntp> postscript to set up NTP server for service nodes.
=item B<-h|--help>

View File

@@ -61,11 +61,11 @@ To list the contents of the xCAT osimage definition use the xCAT B<lsdef> comman
To check the validity of a SPOT or lpp_source resource
To remove an xCAT osimage definition along with the associated NIM resource definitions use the B<rmnimimage> command. Be careful not to accidently remove NIM resources if they are still needed.
To remove an xCAT osimage definition along with the associated NIM resource definitions use the B<rmnimimage> command. Be careful not to accidentally remove NIM resources if they are still needed.
To list a NIM resource definition use the AIX B<lsnim> command ("lsnim -l <resource_name>").
To check the validity of a SPOT or lpp_source resource use the AIX B<nim> command ("nim -o check <resourec-name>").
To check the validity of a SPOT or lpp_source resource use the AIX B<nim> command ("nim -o check <resource-name>").
To remove specific NIM resource definitions use the AIX B<nim> command. ("nim -o remove <resource-name>").

View File

@@ -90,7 +90,7 @@ Request to create a new full system partition for each CEC.
To specify the parameters which are used to create a partition. The I<vmcpus>, I<vmmemory> are necessary, and the value specified with this command have a more high priority. If the value of any of the three options is not specified, the corresponding value specified for the node object will be used. If any of the three attributes is neither specified with this command nor specified with the node object, error information will be returned. To reference to L<lsvm(1)|lsvm.1> for more information about 'drc_index' for I<vmphyslots>.
The option I<vios> is used to specify the partition that will be created is a VIOS partition. If specified, the value for I<vmstorage> shall be number which indicate the number of vSCSI server adapter will be created, and if no value specified for I<vmphyslots>, all the physical slot of the power machine will be asigned to VIOS partition. If not specified, it shall be in form of I<vios_name:server_slotid> to specify the vios and the virtual slot id of the vSCSI server adapter that will be connected from the Logical partition.
The option I<vios> is used to specify the partition that will be created is a VIOS partition. If specified, the value for I<vmstorage> shall be number which indicate the number of vSCSI server adapter will be created, and if no value specified for I<vmphyslots>, all the physical slot of the power machine will be assigned to VIOS partition. If not specified, it shall be in form of I<vios_name:server_slotid> to specify the vios and the virtual slot id of the vSCSI server adapter that will be connected from the Logical partition.
=item B<-f|--force>

View File

@@ -27,7 +27,7 @@ I<noderange> is the nodes to be monitored. If omitted, all nodes will be monitor
B<-h | --help> Display usage message.
B<-r | --remote> Specifies that the operation will also be performed on the nodes. For example, the3rd party monitoring software daemons on the nodes will also be started.
B<-r | --remote> Specifies that the operation will also be performed on the nodes. For example, the 3rd party monitoring software daemons on the nodes will also be started.
B<-v | --version> Command Version.

View File

@@ -27,7 +27,7 @@ I<noderange> is the nodes to be stopped for monitoring. If omitted, all nodes wi
B<-h | -help> Display usage message.
B<-r | --remote> Specifies that the operation will also be performed on the nodes. For example, the3rd party monitoring software daemons on the nodes will also be stopped.
B<-r | --remote> Specifies that the operation will also be performed on the nodes. For example, the 3rd party monitoring software daemons on the nodes will also be stopped.
B<-v | -version> Command Version.