arif/xcat-core
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed xcatconfig man page formatting problems

Browse Source 
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@4063 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
bp-sawyers 2009-08-31 19:16:59 +00:00
parent 279f00ca1e
commit e5786506f0
1 changed files with 4 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
xCAT-client/pods/man8/xcatconfig.8.pod
View File

@ -1,6 +1,6 @@
=head1 NAME
B<xcatconfig> - Sets up the Managment Node during the xCAT install.
B<xcatconfig> - Sets up the Management Node during the xCAT install.
=head1 SYNOPSIS
@ -18,11 +18,10 @@ B<xcatconfig> {B<-k>|B<--sshkeys>} {B<-s>|B<--sshnodehostkeys>} {B<-c>|B<--crede
B<xcatconfig> {B<-f>|B<--force>}
=head1 DESCRIPTION
B<xcatconfig> Performs basic xCAT setup operations on an xCAT management node. This command should not be run on an xCAT Service Node, unless you are making it a Management Node. See flag description below for more details.
=head1 OPTIONS
=over 6
@ -43,7 +42,6 @@ The install option is normally run as a post operation from the rpm xCAT.spec fi
The update install option is normally run as a post operation from the rpm xCAT.spec file during an update install of xCAT on the Management Node. It will check the setup the root ssh keys, ssh node keys, xCAT credentials, datebase, exported directories, syslog and the state of daemons needed by xCAT, after the updateinstall of xCAT. If setup is required, it will perform the operation. It will restart the necessary daemons.
=item B<-k> I<sshkeys>
This option will remove and regenerate the root id_rsa keys. It should only be used, if the keys are deleted or corrupted. The key must then be distribute to the nodes by installing or using xdsh -K option, for root to be able to ssh to the nodes without being prompted for a password.
@ -53,22 +51,19 @@ rspconfig will need to be run to distribute the key to the MM and HMCs. Any devi
This option will remove and regenerate the node host ssh keys. It should only be used, if the keys are deleted or are corrupted. The keys must then be redistribute to the nodes by installing or using xdcp or pcp to copy the keys from /etc/xcat/hostkeys directory to the /etc/ssh directory on the nodes.
=item B<-c> I<credentials>
This option will remove and regenerate the xCAT credentials. It should only be used, if they are deleted or become corrupted. The credentials must be redistribed to the service nodes by installing the service node. makeconservercf must be rerun to pick up the new credentials, and conserver must be stop and started.
=item B<-d> I<datebase>
=item B<-d> I<database>
This option will reinitialize the basic xCAT database table setup. It will not remove any new database entries that have been added, but it is strongly suggested that you backup you database (dumpxCATdb) before using it.
=item B<-f> I<force>
The force option may be used after the install to reinitialize the Management Node. This option will regenerate keys, credential and reinititialize the site table. This option should be used, if keys or credentials become corrupt or lost.
Additional action must be taken after using the force options. ssh keys must be redistributed to the nodes, site table attributes might need to be restored, makeconservercf needs to be rerun to pick up the new credentials and conserver stoped and started, rspconfig needs to be rerun to distribute the new keys to the MM and the HMCs.
A new set of common ssh host keys will have been generated for the nodes. If you wish your nodes to be able to ssh to each other with out password intervention, then you should redistribute these new keys to the nodes. You can do this my reinstalling the nodes, or by xdcp or pcp /etc/xcat/hostkeys/* to the /etc/ssh directory on all nodes. If the nodes hostkeys are updated then you will need to remove their entries from the known_hosts files on the managment node before using ssh, xdsh, xdcp.
A new set of common ssh host keys will have been generated for the nodes. If you wish your nodes to be able to ssh to each other with out password intervention, then you should redistribute these new keys to the nodes. You can do this my reinstalling the nodes, or by xdcp or pcp /etc/xcat/hostkeys/* to the /etc/ssh directory on all nodes. If the nodes hostkeys are updated then you will need to remove their entries from the known_hosts files on the management node before using ssh, xdsh, xdcp.
For a service node, it is probably best to re-install the service node to make sure the correct keys and credentials are picked up for node installs.
=back
@ -89,7 +84,6 @@ To regenerate root's ssh keys:
B<xcatconfig> I<-k>
=item *
To regenerate node host ssh keys:
@ -102,7 +96,4 @@ To regenerate node host ssh keys and credentials:
B<xcatconfig> I<-s> I<-c>
=back