exclude repeated headings from TOC

This commit is contained in:
Christopher Engelhard 2020-07-26 20:35:01 +02:00 committed by lcts
parent 98ad2b7901
commit 363b51c427
5 changed files with 12 additions and 1 deletions

View file

@ -3,12 +3,14 @@
Older versions of Fedora use SysVinit scripts to manage services. This section provides some guidelines on how to convert a SysVinit script to a systemd equivalent.
[discrete]
== Prerequisites
* You are logged in as a user with administrator-level permissions.
* You have a custom SysVinit script to convert to a systemd configuration.
[discrete]
== Procedure
. Identify the runlevels in your SysVinit script. This is usually defined with `chkconfig` directive in the commented section at the beginning of the script. For example, the following indicates the service is using runlevels 3, 4, and 5:
@ -91,6 +93,7 @@ Alternatively, you can omit `ExecStop` and use the default behavior, which kills
. Review the SysVinit script and identify any additional parameters or functions. Use systemd parameters to replicate any identified SysVinit functions that might be relevant to your service.
[discrete]
== Related Information
* See link:#common-service-parameters[Common service parameters] for more information about the parameters used in this procedure.

View file

@ -3,10 +3,12 @@
This example shows how to create a unit file for a custom service. Custom unit files are located in `/etc/systemd/system/` and have a `.service` extension. For example, a custom `foo` service uses `/etc/systemd/system/foo.service` unit file.
[discrete]
== Prerequisites
* You are logged in as a user with administrator-level permissions.
[discrete]
== Procedure
This procedure creates a basic configuration file to control the `foo` service.
@ -92,6 +94,7 @@ $ systemctl status foo
Dec 14 14:09:12 dansmachine systemd[1]: Started My custom service.
----
[discrete]
== Related Information
* See link:#common-service-parameters[Common service parameters] for more information about the parameters used in this procedure.

View file

@ -3,12 +3,14 @@
This example shows how to modify an existing service. The files for service modification are stored in a directory within `/etc/systemd/system`. This directory is named after the service. For example, this procedure modifies the `httpd` service.
[discrete]
== Prerequisites
* You are logged in as a user with administrator-level permissions.
* You have a configured `httpd` server running through systemd.
[discrete]
== Procedure
. Create a directory for the service modification in the following format: `[SERVICE NAME].service.d`. For example, the directory for the `httpd.service` modification is `httpd.service.d`:
@ -39,6 +41,7 @@ RestartSec=30
# systemctl restart httpd
----
[discrete]
== Related Information
* See link:#common-service-parameters[Common service parameters] for more information about the parameters used in this procedure.

View file

@ -3,10 +3,12 @@
You can perform various management tasks to control systemd services using the `systemctl` command. The following is a set of example commands to demonstrate how to use `systemctl` to manage systemd services.
[discrete]
== Prerequisites
You are logged in as a user with administrator-level permissions.
[discrete]
== Procedure
The following commands control the `foo` service:
@ -59,6 +61,7 @@ The following commands control the `foo` service:
# systemctl is-enabled foo
----
[discrete]
== Related Information
* Run `man systemctl` for more details.

View file

@ -27,7 +27,6 @@ include::{partialsdir}/ref_mapping-runlevel-to-targets.adoc[leveloffset=+1]
include::{partialsdir}/ref_mapping-service-commands.adoc[leveloffset=+1]
[discrete]
== Additional resources
* http://www.freedesktop.org/wiki/Software/systemd[Project homepage]