Andreas Jaeger 2d44b2b36d Prepare for Sphinx 1.5

The new sphinx version introduces some changes that break build:

* Warns if code cannot be parsed for highlighting. Fix the code so
  that it can be parsed, this includes uncommenting "..." lines.
  Note that not every config file is an ini-file.
  Also, the parser seems to have bugs and cannot parse all files.
  Fix mysql ini file and enable the parameter, see
http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_file_per_table
* :option: works only with declared options, replace useage with
  simple ``.

This change only handles a few files, more to come later.

Change-Id: I7c7335e514581622dd562ee355f62d6ae1beaa18

2017-01-11 20:37:55 +01:00

2.6 KiB

Raw Blame History

Controller node

Perform these steps on the controller node.

Install and configure components

Install the packages:

ubuntu or debian

# apt install chrony

rdo

# yum install chrony

obs

# zypper install chrony

ubuntu or debian

Edit the /etc/chrony/chrony.conf file and add, change, or remove these keys as necessary for your environment:
```
server NTP_SERVER iburst
```
Replace NTP_SERVER with the hostname or IP address of a suitable more accurate (lower stratum) NTP server. The configuration supports multiple server keys.

Note

By default, the controller node synchronizes the time via a pool of public servers. However, you can optionally configure alternative servers such as those provided by your organization.
To enable other nodes to connect to the chrony daemon on the controller node, add this key to the /etc/chrony/chrony.conf file:
```
allow 10.0.0.0/24
```
Restart the NTP service:
```
# service chrony restart
```

rdo or obs

Edit the /etc/chrony.conf file and add, change, or remove these keys as necessary for your environment:
```
server NTP_SERVER iburst
```
Replace NTP_SERVER with the hostname or IP address of a suitable more accurate (lower stratum) NTP server. The configuration supports multiple server keys.

Note

By default, the controller node synchronizes the time via a pool of public servers. However, you can optionally configure alternative servers such as those provided by your organization.
To enable other nodes to connect to the chrony daemon on the controller node, add this key to the /etc/chrony.conf file:
```
allow 10.0.0.0/24
```
If necessary, replace 10.0.0.0/24 with a description of your subnet.
Start the NTP service and configure it to start when the system boots:
```
# systemctl enable chronyd.service
# systemctl start chronyd.service
```

2.6 KiB Raw Blame History

Controller node

Install and configure components

2.6 KiB

Raw Blame History