From 9ed8fdc095bfb56af35c82ffcd9c3ffc70d874fb Mon Sep 17 00:00:00 2001 From: Matthew Miller Date: Mon, 26 Feb 2018 17:43:59 +0100 Subject: [PATCH] =?UTF-8?q?Systemd=20=E2=86=92=20systemd?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- en-US/debug-systemd-problems.adoc | 8 ++++---- en-US/modules/con_understanding-systemd.adoc | 16 ++++++++-------- .../proc_converting-sysvinit-services.adoc | 12 ++++++------ .../proc_creating-new-systemd-services.adoc | 12 ++++++------ ...proc_modifying-existing-systemd-services.adoc | 4 ++-- ...g-stopping-and-querying-systemd-services.adoc | 4 ++-- en-US/modules/ref_common-service-parameters.adoc | 14 +++++++------- .../modules/ref_mapping-runlevel-to-targets.adoc | 6 +++--- en-US/modules/ref_mapping-service-commands.adoc | 6 +++--- en-US/postgresql.adoc | 2 +- .../understanding-and-administering-systemd.adoc | 4 ++-- en-US/wine.adoc | 2 +- 12 files changed, 45 insertions(+), 45 deletions(-) diff --git a/en-US/debug-systemd-problems.adoc b/en-US/debug-systemd-problems.adoc index fad7ffd..4baf3f0 100644 --- a/en-US/debug-systemd-problems.adoc +++ b/en-US/debug-systemd-problems.adoc @@ -1,11 +1,11 @@ -= How to debug Systemd problems += How to debug systemd problems ''' [IMPORTANT] ====== -This page was automatically converted from https://fedoraproject.org/wiki/How_to_debug_Systemd_problems +This page was automatically converted from https://fedoraproject.org/wiki/How_to_debug_systemd_problems It is probably @@ -33,7 +33,7 @@ with the following macro: *Foreword* -If you are experiencing a problem with system boot up due to Systemd, +If you are experiencing a problem with system boot up due to systemd, please see the link:Bugs/Common[common bugs] document before filing a bug. Some easy configuration tweaks that fix a wide range of issues may be listed there. If the problem you are seeing is not listed there or @@ -88,7 +88,7 @@ To examine what gets started when when booted into a specific target. ( In the above example the multi-user.target ) [[systemd-boot-parameters]] -Systemd boot parameters +systemd boot parameters ----------------------- The following boot parameters are also available to further assist with diff --git a/en-US/modules/con_understanding-systemd.adoc b/en-US/modules/con_understanding-systemd.adoc index 93f6dda..42b630d 100644 --- a/en-US/modules/con_understanding-systemd.adoc +++ b/en-US/modules/con_understanding-systemd.adoc @@ -1,7 +1,7 @@ [id='understanding-systemd'] -= 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 @@ -10,9 +10,9 @@ Systemd is a system and service manager for Linux, compatible with SysV and LSB * Maintains mount and automount points * Implements an elaborate transactional dependency-based service control logic. -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. +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 _units_, which are representations of system resources and services. This following list shows the unit types that Systemd can manage: +systemd manages _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. @@ -21,10 +21,10 @@ socket:: A network socket associated with a service. device:: - A device specifically managed with Systemd. + A device specifically managed with systemd. mount:: - A mountpoint managed with Systemd. + A mountpoint managed with systemd. automount:: A mountpoint automatically mounted on boot. @@ -42,10 +42,10 @@ timer:: A timer to schedule activation of another unit. snapshot:: - A snapshot of the current Systemd state. Usually used to rollback after making temporary changes to Systemd. + A snapshot of the current systemd state. Usually used to rollback after making temporary changes to systemd. slice:: Restrivtion of resources through Linux Control Group nodes (cgroups). scope:: - Information from Systemd bus interfaces. Usually used to manage external system processes. + Information from systemd bus interfaces. Usually used to manage external system processes. diff --git a/en-US/modules/proc_converting-sysvinit-services.adoc b/en-US/modules/proc_converting-sysvinit-services.adoc index fdd2143..0ca4ae8 100644 --- a/en-US/modules/proc_converting-sysvinit-services.adoc +++ b/en-US/modules/proc_converting-sysvinit-services.adoc @@ -1,13 +1,13 @@ [#converting-sysvinit-services] = Converting SysVinit services -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. +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. .Prerequisites * You are logged in as a user with administrator-level permissions. -* You have a custom SysVinit script to convert to a Systemd configuration. +* You have a custom SysVinit script to convert to a systemd configuration. .Procedure @@ -17,14 +17,14 @@ Older versions of Fedora use SysVinit scripts to manage services. This section p # chkconfig: 235 20 80 ---- + -Systemd uses targets instead of runlevels. Use the table in <<#converting-sysvinit-services>> to map the runlevels to targets. In this example, runlevels 2, 3, and 5 are all multi-user runlevels, so the Systemd service can use the following: +systemd uses targets instead of runlevels. Use the table in <<#converting-sysvinit-services>> to map the runlevels to targets. In this example, runlevels 2, 3, and 5 are all multi-user runlevels, so the systemd service can use the following: + ---- [Install] WantedBy=multi-user.target ---- + -If you enable the custom Systemd service to start at boot (`systemctl enable foo.service`), Systemd loads the service when loading the `multi-user.target` at boot time. +If you enable the custom systemd service to start at boot (`systemctl enable foo.service`), systemd loads the service when loading the `multi-user.target` at boot time. . Identify the dependent services and targets. For example, if the custom service requires network connectivity, specify the `network.target` as a dependency: + @@ -34,7 +34,7 @@ Description=My custom service Requires=network.target ---- -. Identify the command used to start the service in the SysVinit script and convert this to the Systemd equivalent. For example, the script might contain a `start` function in the following format: +. Identify the command used to start the service in the SysVinit script and convert this to the systemd equivalent. For example, the script might contain a `start` function in the following format: + [source,bash] ---- @@ -89,7 +89,7 @@ ExecStop=/usr/bin/myservice shutdown + Alternatively, you can omit `ExecStop` and use the default behavior, which kills the service. -. 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. +. 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. .Related Information diff --git a/en-US/modules/proc_creating-new-systemd-services.adoc b/en-US/modules/proc_creating-new-systemd-services.adoc index 651fa7d..9287317 100644 --- a/en-US/modules/proc_creating-new-systemd-services.adoc +++ b/en-US/modules/proc_creating-new-systemd-services.adoc @@ -1,5 +1,5 @@ [#creating-new-systemd-services] -= Creating new Systemd services += Creating new systemd services 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. @@ -22,9 +22,9 @@ 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. + 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. + The resulting `[Unit]` section looks like this: + @@ -37,7 +37,7 @@ Requires=network.target .. The `[Service]` section provides instructions on how to control the service. The `foo` service uses the following parameters: + `Type`:: - Defines the type of Systemd service. In this example, the `foo` service is a `simple` service, which starts the service without any special consideration. + Defines the type of systemd service. In this example, the `foo` service is a `simple` service, which starts the service without any special consideration. `ExecStart`:: The command to run to start the service. This includes the full path to the command and arguments to modify the service. + @@ -49,10 +49,10 @@ Type=simple ExecStart=/usr/bin/sleep infinity ---- -.. The `[Install]` section provides instructions on how Systemd installs the service. The `foo` service uses the following parameters: +.. The `[Install]` section provides instructions on how systemd installs the service. The `foo` service uses the following parameters: + `WantedBy`:: - Defines which service triggers the custom service if enabled with `systemctl enable`. This is mostly used for starting the custom service on boot. In this example, `foo.service` uses `multi-user.target`, which starts `foo.service` when Systemd loads `multi-user.target` on boot. + Defines which service triggers the custom service if enabled with `systemctl enable`. This is mostly used for starting the custom service on boot. In this example, `foo.service` uses `multi-user.target`, which starts `foo.service` when systemd loads `multi-user.target` on boot. . The full `foo.service` file contains the following contents: + diff --git a/en-US/modules/proc_modifying-existing-systemd-services.adoc b/en-US/modules/proc_modifying-existing-systemd-services.adoc index 8c6ea19..4c41298 100644 --- a/en-US/modules/proc_modifying-existing-systemd-services.adoc +++ b/en-US/modules/proc_modifying-existing-systemd-services.adoc @@ -1,5 +1,5 @@ [#modifying-existing-systemd-services] -= Modifying existing Systemd services += Modifying existing systemd services 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. @@ -7,7 +7,7 @@ This example shows how to modify an existing service. The files for service modi * You are logged in as a user with administrator-level permissions. -* You have a configured `httpd` server running through Systemd. +* You have a configured `httpd` server running through systemd. .Procedure diff --git a/en-US/modules/proc_starting-stopping-and-querying-systemd-services.adoc b/en-US/modules/proc_starting-stopping-and-querying-systemd-services.adoc index 31f5af6..0a89d77 100644 --- a/en-US/modules/proc_starting-stopping-and-querying-systemd-services.adoc +++ b/en-US/modules/proc_starting-stopping-and-querying-systemd-services.adoc @@ -1,7 +1,7 @@ [#starting-stopping-and-querying-systemd-services] -= Starting, stopping, and querying Systemd services += Starting, stopping, and querying systemd services -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. +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. .Prerequisites diff --git a/en-US/modules/ref_common-service-parameters.adoc b/en-US/modules/ref_common-service-parameters.adoc index 04961c5..619deea 100644 --- a/en-US/modules/ref_common-service-parameters.adoc +++ b/en-US/modules/ref_common-service-parameters.adoc @@ -3,7 +3,7 @@ .Unit Parameters -This section contains parameters you can use in the `[Unit]` section of a service. These parameters are common to other Systemd units. +This section contains parameters you can use in the `[Unit]` section of a service. These parameters are common to other systemd units. This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`. @@ -14,7 +14,7 @@ Documentation:: A space-separated list of URIs referencing documentation for this service or its configuration. Accepted are only URIs of the following types: `http://`, `https://`, `file:`, `info:`, `man:`. Requires:: - Configures requirement dependencies on other services. If this service gets activated, the units listed here are activated too. If one of the dependent services fails to activate, Systemd does not start this service. This option may be specified more than once or you can specify multiple space-separated units. + Configures requirement dependencies on other services. If this service gets activated, the units listed here are activated too. If one of the dependent services fails to activate, systemd does not start this service. This option may be specified more than once or you can specify multiple space-separated units. Wants:: Similar to `Requires`, except failed units do not have any effect on the service. @@ -36,7 +36,7 @@ OnFailure:: .Install Parameters -This section contains parameters you can use in the `[Install]` section of a service. These parameters are common to other Systemd units. +This section contains parameters you can use in the `[Install]` section of a service. These parameters are common to other systemd units. This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`. @@ -51,7 +51,7 @@ Also:: .Service Parameters -This section contains parameters you can use in the `[Service]` section of a service unit. These parameters are specific only to Systemd service units. +This section contains parameters you can use in the `[Service]` section of a service unit. These parameters are specific only to systemd service units. This list is a summarized version. For a full list of these parameters and their descriptions, run `man systemd.unit`. @@ -60,7 +60,7 @@ Type:: + * `simple` - The service starts as the main process. This is the default. * `forking` - The service calls forked processes and run as part of the main daemon. -* `oneshot` - Similar to `simple`, except the process must exits before Systemd starts follow-up services. +* `oneshot` - Similar to `simple`, except the process must exits before systemd starts follow-up services. * `dbus` - Similar to `simple`, except the daemon acquires a name of the D-Bus bus. * `notify` - Similar to `simple`, except the daemon sends a motification message using `sd_notify` or an equivalent call after starting up. * `idle` - Similar to `simple`, except the execution of the service is delayed until all active jobs are dispatched. @@ -69,10 +69,10 @@ RemainAfterExit:: A boolean value that specifies whether the service shall be considered active even if all its processes exited. Defaults to no. 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. + 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/en-US/modules/ref_mapping-runlevel-to-targets.adoc b/en-US/modules/ref_mapping-runlevel-to-targets.adoc index df4c56c..7e30b58 100644 --- a/en-US/modules/ref_mapping-runlevel-to-targets.adoc +++ b/en-US/modules/ref_mapping-runlevel-to-targets.adoc @@ -1,16 +1,16 @@ [#mapping-runlevels-to-targets] = Mapping runlevels to targets -Systemd targets serve a similar purpose to SysVinit runlevels but act a little different. 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 different. 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. -The following is a mapping of SysVinit runlevels to Systemd targets. +The following is a mapping of SysVinit runlevels to systemd targets. [cols="2,5,5",options="header"] .Runlevel to target mapping |=== -|Sysvinit Runlevel |Systemd Target |Notes +|Sysvinit Runlevel |systemd Target |Notes |0 |runlevel0.target, poweroff.target |Halt the system. diff --git a/en-US/modules/ref_mapping-service-commands.adoc b/en-US/modules/ref_mapping-service-commands.adoc index 3458359..9226fc8 100644 --- a/en-US/modules/ref_mapping-service-commands.adoc +++ b/en-US/modules/ref_mapping-service-commands.adoc @@ -1,13 +1,13 @@ [#mapping-service-commands] = Mapping service commands -The following table demonstrates the Systemd equivalent of SysVinit commands. +The following table demonstrates the systemd equivalent of SysVinit commands. NOTE: All recent versions of systemctl assume the `.service` suffix if left off the service name. For example, `systemctl start frobozz.service` is the same as `systemctl start frobozz`. [cols=",,",options="header",] |=== -|Sysvinit Command |Systemd Command |Notes +|Sysvinit Command |systemd Command |Notes |`service frobozz start`|`systemctl start frobozz`|Used to start a service (not reboot persistent) |`service frobozz stop`|`systemctl stop frobozz`|Used to stop a service (not reboot persistent) @@ -39,4 +39,4 @@ Used to list all the services and other units |`chkconfig frobozz --add`|`systemctl daemon-reload`|Used when you create a new service file or modify any configuration |=== -NOTE: All `/sbin/service` and `/sbin/chkconfig` commands listed in the table continue to work on Systemd-based systems and are translated to native equivalents as necessary. The only exception is `chkconfig --list`. +NOTE: All `/sbin/service` and `/sbin/chkconfig` commands listed in the table continue to work on systemd-based systems and are translated to native equivalents as necessary. The only exception is `chkconfig --list`. diff --git a/en-US/postgresql.adoc b/en-US/postgresql.adoc index 1032941..446b418 100644 --- a/en-US/postgresql.adoc +++ b/en-US/postgresql.adoc @@ -251,7 +251,7 @@ Note: changing PGPORT or PGDATA will typically require adjusting SELinux configuration as well; see section selinux. Please follow the systemd documentation -http://fedoraproject.org/wiki/Systemd#How_do_I_customize_a_unit_file.2F_add_a_custom_unit_file.3F[2] +http://fedoraproject.org/wiki/systemd#How_do_I_customize_a_unit_file.2F_add_a_custom_unit_file.3F[2] for more details. [[postgresql.conf]] diff --git a/en-US/understanding-and-administering-systemd.adoc b/en-US/understanding-and-administering-systemd.adoc index 6589e9b..d8101f9 100644 --- a/en-US/understanding-and-administering-systemd.adoc +++ b/en-US/understanding-and-administering-systemd.adoc @@ -1,9 +1,9 @@ :source-highlighter: prettify [id='understanding-and-administering-systemd'] -= Understanding and administering Systemd += Understanding and administering systemd -Learn the basic principles of Systemd: how to configure it and use to administer the system. +Learn the basic principles of systemd: how to configure it and use to administer the system. include::en-US/modules/con_understanding-systemd.adoc[leveloffset=+1] diff --git a/en-US/wine.adoc b/en-US/wine.adoc index 7594f3b..42db2f8 100644 --- a/en-US/wine.adoc +++ b/en-US/wine.adoc @@ -91,7 +91,7 @@ wine |_wine-symbol-fonts_ |Wine Symbol font family -|_wine-systemd_ |Systemd configuration for the wine binfmt handler +|_wine-systemd_ |systemd configuration for the wine binfmt handler |_wine-system-fonts_ |Wine System font family