xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-05-22 11:42:05 +00:00
Code Issues Releases Wiki Activity

Fix restartxcatd man pages

Browse Source
This commit is contained in:
Mark Gurevich 2019-06-17 15:07:52 -04:00
parent 2c5e727be7
commit 1e7cc676af
2 changed files with 33 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/source/guides/admin-guides/references/man1/restartxcatd.1.rst
View File

@ -29,21 +29,28 @@ DESCRIPTION
The \ **restartxcatd**\ command restarts the xCAT daemon (xcatd).
\ **Linux Specific**\
\ **Linux Specific**\ :
It will perform the xcatd \ *fast restart*\ . The xcatd \ *fast restart*\ is a specific restart which has two advantages compares to the \ *stop*\ and then \ *start*\ .
1. The interval of xcatd out of service is very short.
2. The in processing request which initiated by old xcatd will not be stopped by force. The old xcatd will hand over the sockets to new xcatd, but old xcat will still be waiting for the in processing request to finish before the exit.
It does the same thing as 'service xcatd restart' on NON-systemd enabled Operating System like rh6.x and sles11.x. But for the systemd enabled Operating System like rh7 and sles12, the 'service xcatd restart' just do the \ *stop*\ and \ *start*\ instead of xcatd \ *fast restart*\ .
It's recommended to use \ **restartxcatd**\ command to restart xcatd on systemd enable system like rh7 and sles12 instead of 'service xcatd restart' or 'systemctl restart xcatd'.
\ **AIX Specific**\
It runs 'stopsrc -s xcatd' to stop xcatd first if xcatd is active, then runs 'startsrc -s xcatd' to start xcatd.
1. The interval of xcatd out of service is very short.
2. The in processing request which initiated by old xcatd will not be stopped by force. The old xcatd will hand over the sockets to new xcatd, but old xcat will still be waiting for the in processing request to finish before the exit.
It does the same thing as \ **service xcatd restart**\ on NON-systemd enabled Operating System like rh6.x and sles11.x. But for the systemd enabled Operating System like rh7 and sles12, the \ **service xcatd restart**\ will just do the \ *stop*\ and \ *start*\ instead of xcatd \ *fast restart*\ .
It's recommended to use \ **restartxcatd**\ command to restart xcatd on systemd enabled system like rh7 and sles12 instead of \ **service xcatd restart**\ or \ **systemctl restart xcatd**\ .
\ **AIX Specific**\ :
It runs \ **stopsrc -s xcatd**\ to stop xcatd first if xcatd is active, then runs \ **startsrc -s xcatd**\ to start xcatd.
If the xcatd subsystem was not created, \ **restartxcatd**\ will create it automatically.

26
xCAT-client/pods/man1/restartxcatd.1.pod
View File

@ -11,25 +11,31 @@ B<restartxcatd> [[B<-h>|B<--help>] | [B<-v>|B<--version>] | [B<-r>|B<--reload>]]
The B<restartxcatd> command restarts the xCAT daemon (xcatd).
B<Linux Specific>
B<Linux Specific>:
=over 4
It will perform the xcatd I<fast restart>. The xcatd I<fast restart> is a specific restart which has two advantages compares to the I<stop> and then I<start>.
=over 2
It will perform the xcatd I<fast restart>. The xcatd I<fast restart> is a specific restart which has two advantages compares to the I<stop> and then I<start>.
1. The interval of xcatd out of service is very short.
2. The in processing request which initiated by old xcatd will not be stopped by force. The old xcatd will hand over the sockets to new xcatd, but old xcat will still be waiting for the in processing request to finish before the exit.
=item 1. The interval of xcatd out of service is very short.
It does the same thing as 'service xcatd restart' on NON-systemd enabled Operating System like rh6.x and sles11.x. But for the systemd enabled Operating System like rh7 and sles12, the 'service xcatd restart' just do the I<stop> and I<start> instead of xcatd I<fast restart>.
It's recommended to use B<restartxcatd> command to restart xcatd on systemd enable system like rh7 and sles12 instead of 'service xcatd restart' or 'systemctl restart xcatd'.
=item 2. The in processing request which initiated by old xcatd will not be stopped by force. The old xcatd will hand over the sockets to new xcatd, but old xcat will still be waiting for the in processing request to finish before the exit.
=back
B<AIX Specific>
It does the same thing as B<service xcatd restart> on NON-systemd enabled Operating System like rh6.x and sles11.x. But for the systemd enabled Operating System like rh7 and sles12, the B<service xcatd restart> will just do the I<stop> and I<start> instead of xcatd I<fast restart>.
=over 2
It's recommended to use B<restartxcatd> command to restart xcatd on systemd enabled system like rh7 and sles12 instead of B<service xcatd restart> or B<systemctl restart xcatd>.
It runs 'stopsrc -s xcatd' to stop xcatd first if xcatd is active, then runs 'startsrc -s xcatd' to start xcatd.
=back
B<AIX Specific>:
=over 4
It runs B<stopsrc -s xcatd> to stop xcatd first if xcatd is active, then runs B<startsrc -s xcatd> to start xcatd.
If the xcatd subsystem was not created, B<restartxcatd> will create it automatically.