diff --git a/modules/ROOT/pages/_partials/con_understanding-systemd.adoc b/modules/ROOT/pages/_partials/con_understanding-systemd.adoc index 0c9bb30..784d3c0 100644 --- a/modules/ROOT/pages/_partials/con_understanding-systemd.adoc +++ b/modules/ROOT/pages/_partials/con_understanding-systemd.adoc @@ -1,7 +1,7 @@ [id='understanding-systemd'] = Understanding systemd -_systemd_ is a system and service manager for Linux, compatible with SysV and LSB init scripts. _systemd_ provides: +_Systemd_ is a system and service manager for Linux, compatible with SysV and LSB init scripts. _Systemd_ provides: * Aggressive parallelization capabilities * Uses socket and D-Bus activation for starting services @@ -12,7 +12,7 @@ _systemd_ is a system and service manager for Linux, compatible with SysV and LS The `systemctl` command is the primary tool to manage _systemd_. It combines the functionality of SysVinit's `service` and `chkconfig` commands into a single tool you can use to enable and disable services permanently or only for the current session. -_systemd_ manages so-called *_units_*, which are representations of system resources and services. This following list shows the unit types that _systemd_ can manage: +_Systemd_ manages so-called *_units_*, which are representations of system resources and services. This following list shows the unit types that _systemd_ can manage: service:: A service on the system, including instructions for starting, restarting, and stopping the service. diff --git a/modules/ROOT/pages/_partials/proc_creating-new-systemd-services.adoc b/modules/ROOT/pages/_partials/proc_creating-new-systemd-services.adoc index f5b619e..b43e0f4 100644 --- a/modules/ROOT/pages/_partials/proc_creating-new-systemd-services.adoc +++ b/modules/ROOT/pages/_partials/proc_creating-new-systemd-services.adoc @@ -24,7 +24,7 @@ This procedure creates a basic configuration file to control the `foo` service. .. The `[Unit]` section provides basic information about the service. The `foo` service uses the following parameters: + `Description`:: - A string describing the unit. _systemd_ displays this description next to the unit name in the user interface. + A string describing the unit. _Systemd_ displays this description next to the unit name in the user interface. `Requires`:: Defines unit to use as a dependency for the service. If you activate the unit, _systemd_ activates the units listed in `Requires` as well. For example, the `foo` service might require network connectivity, which means the `foo` services requires `network.target` as a dependency. + diff --git a/modules/ROOT/pages/_partials/ref_common-service-parameters.adoc b/modules/ROOT/pages/_partials/ref_common-service-parameters.adoc index cce2d3f..7b40f46 100644 --- a/modules/ROOT/pages/_partials/ref_common-service-parameters.adoc +++ b/modules/ROOT/pages/_partials/ref_common-service-parameters.adoc @@ -72,7 +72,7 @@ GuessMainPID:: A boolean value that specifies whether _systemd_ should guess the main PID of a service if it cannot be determined reliably. This option is ignored unless `Type=forking` is set and `PIDFile` is not set. Defaults to yes. PIDFile:: - An absolute filename pointing to the PID file of this daemon. Use of this option is recommended for services where `Type=forking`. _systemd_ reads the PID of the main process of the daemon after start-up of the service. _systemd_ does not write to the file configured here, although it removes the file after the service has shut down. + An absolute filename pointing to the PID file of this daemon. Use of this option is recommended for services where `Type=forking`. _Systemd_ reads the PID of the main process of the daemon after start-up of the service. _Systemd_ does not write to the file configured here, although it removes the file after the service has shut down. BusName:: A D-Bus bus name to reach this service. This option is mandatory for services where `Type=dbus`. diff --git a/modules/ROOT/pages/_partials/ref_mapping-runlevel-to-targets.adoc b/modules/ROOT/pages/_partials/ref_mapping-runlevel-to-targets.adoc index 994f146..e661700 100644 --- a/modules/ROOT/pages/_partials/ref_mapping-runlevel-to-targets.adoc +++ b/modules/ROOT/pages/_partials/ref_mapping-runlevel-to-targets.adoc @@ -1,7 +1,7 @@ [#mapping-runlevels-to-targets] = Mapping runlevels to targets -_systemd_ targets serve a similar purpose to SysVinit runlevels but act a little differently. Each target has a name instead of a number and each serves a specific purpose. _systemd_ implements some targets by inheriting all of the services of another target and adding additional services to it. Some _systemd_ targets mimic the common sysvinit runlevels, which means you can switch targets with the familiar `telinit RUNLEVEL` command. The runlevels assigned a specific purpose on vanilla Fedora installs (0, 1, 3, 5, and 6) have a 1:1 mapping with a specific _systemd_ target. +_Systemd_ targets serve a similar purpose to SysVinit runlevels but act a little differently. Each target has a name instead of a number and each serves a specific purpose. _Systemd_ implements some targets by inheriting all of the services of another target and adding additional services to it. Some _systemd_ targets mimic the common sysvinit runlevels, which means you can switch targets with the familiar `telinit RUNLEVEL` command. The runlevels assigned a specific purpose on vanilla Fedora installs (0, 1, 3, 5, and 6) have a 1:1 mapping with a specific _systemd_ target. However, this is not the case for user-defined runlevels 2 and 4. To make use of those runlevels, create a new named _systemd_ target such as `/etc/systemd/system/$YOURTARGET` that takes one of the existing runlevels as a base, make a directory `/etc/systemd/system/$YOURTARGET.wants`, and then symlink the additional services to enable into that directory.