Browse Source

Merge "Fix the inconsistent display of commands"

Jenkins 2 years ago
parent
commit
0435095abc
1 changed files with 51 additions and 15 deletions
  1. 51
    15
      doc/ha-guide/source/controller-ha-pacemaker.rst

+ 51
- 15
doc/ha-guide/source/controller-ha-pacemaker.rst View File

@@ -468,17 +468,36 @@ Note the following:
468 468
 Start Corosync
469 469
 --------------
470 470
 
471
-Corosync is started as a regular system service.
471
+``Corosync`` is started as a regular system service.
472 472
 Depending on your distribution, it may ship with an LSB init script,
473 473
 an upstart job, or a systemd unit file.
474
-Either way, the service is usually named corosync:
474
+Either way, the service is usually named ``corosync``:
475 475
 
476
-- :command:`# /etc/init.d/corosync start` (LSB)
477
-- :command:`# service corosync start` (LSB, alternate)
478
-- :command:`# start corosync` (upstart)
479
-- :command:`# systemctl start corosync` (systemd)
476
+- To start ``corosync`` with the LSB init script:
480 477
 
481
-You can now check the Corosync connectivity with two tools.
478
+  .. code-block:: console
479
+
480
+     # /etc/init.d/corosync start
481
+
482
+- Alternatively:
483
+
484
+  .. code-block:: console
485
+
486
+     # service corosync start
487
+
488
+- To start ``corosync`` with upstart:
489
+
490
+  .. code-block:: console
491
+
492
+     # start corosync
493
+
494
+- To start ``corosync`` with systemd unit file:
495
+
496
+  .. code-block:: console
497
+
498
+     # systemctl start corosync
499
+
500
+You can now check the ``corosync`` connectivity with one of these tools.
482 501
 
483 502
 Use the :command:`corosync-cfgtool` utility with the :option:`-s` option
484 503
 to get a summary of the health of the communication rings:
@@ -524,21 +543,38 @@ give the command for Corosync version 1?]
524 543
 Start Pacemaker
525 544
 ---------------
526 545
 
527
-After the Corosync services have been started
546
+After the ``corosync`` service have been started
528 547
 and you have verified that the cluster is communicating properly,
529
-you can start :command:`pacemakerd`, the Pacemaker master control process:
548
+you can start :command:`pacemakerd`, the Pacemaker master control process.
549
+Choose one from the following four ways to start it:
550
+
551
+- To start ``pacemaker`` with the LSB init script:
552
+
553
+  .. code-block:: console
554
+
555
+     # /etc/init.d/pacemaker start
556
+
557
+- Alternatively:
558
+
559
+  .. code-block:: console
560
+
561
+     # service pacemaker start
562
+
563
+- To start ``pacemaker`` with upstart:
564
+
565
+  .. code-block:: console
530 566
 
531
-- :command:`# /etc/init.d/pacemaker start` (LSB)
567
+     # start pacemaker
532 568
 
533
-- :command:`# service pacemaker start` (LSB, alternate)
569
+- To start ``pacemaker`` with the systemd unit file:
534 570
 
535
-- :command:`# start pacemaker` (upstart)
571
+  .. code-block:: console
536 572
 
537
-- :command:`# systemctl start pacemaker` (systemd)
573
+     # systemctl start pacemaker
538 574
 
539
-After the Pacemaker services have started,
575
+After the ``pacemaker`` service have started,
540 576
 Pacemaker creates a default empty cluster configuration with no resources.
541
-Use the :command:`crm_mon` utility to observe the status of Pacemaker:
577
+Use the :command:`crm_mon` utility to observe the status of ``pacemaker``:
542 578
 
543 579
 .. code-block:: console
544 580
 

Loading…
Cancel
Save