zimoch/Controls-docs
0
0
Fork 0
forked from Controls/gitea-pages
Code Pull Requests Actions Activity

fix typos

Browse Source
This commit is contained in:
buchel_k
2022-11-21 11:58:34 +01:00
parent 3eeb15d540
commit e8c12569d5
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
rhel8/software.md
+5 -5
View File
@@ -133,14 +133,14 @@ base::timers:
persistence: false
```
For each time following keys are mandatory
For each timer following keys are mandatory
- `description` for a short explaination what it is about
- `command` for the command to run
- `on_calendar` defining when it should run using the [`systemd` calendar event format](https://www.freedesktop.org/software/systemd/man/systemd.time.html#Calendar%20Events), (alternatively see also chapter "CALENDAR EVENTS" `man systemd.date`)
- `on_calendar` defining when it should run using the [`systemd` calendar event format](https://www.freedesktop.org/software/systemd/man/systemd.time.html#Calendar%20Events), (alternatively see also chapter "CALENDAR EVENTS" of `man systemd.date`)
Optional is
- `persistence` which signals if the timer should run immediately after boot when the node was switched of on the last suggested run time (default is `false`)
- `persistence` which signals if the timer should run immediately after boot when the node was switched of on the last scheduled run time (default is `false`)
### Manage Services with Custom Unit Files
@@ -165,9 +165,9 @@ base::services:
```
### Enhance a Service with a Dropin Unit File
It is possible to fine-tune already existing `systemd` unit files with dropins. These are placed as `.conf` files in `/etc/systemd/system/service_name.service.d`.
It is possible to fine-tune already existing `systemd` unit files with dropins. These are placed as `.conf` files in `/etc/systemd/system/$SERVICE.service.d/`.
With the `dropin: true` parameter the content of the `options` parameter is now written into the according dropin directory:
With the `dropin: true` setting the content of the `options` parameter is written into the according dropin directory:
```
base::services:
'name_of_enhanced_service':