From: Lennart Poettering Date: Tue, 5 Jul 2022 12:14:23 +0000 (+0200) Subject: docs: normalize uppercasing of titles of network doc X-Git-Tag: v252-rc1~727 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=e07ed99dd7ef300c0a3fb59133f899668ac2301b;p=thirdparty%2Fsystemd.git docs: normalize uppercasing of titles of network doc --- diff --git a/docs/NETWORK_ONLINE.md b/docs/NETWORK_ONLINE.md index fce4db9c84f..641c5e91298 100644 --- a/docs/NETWORK_ONLINE.md +++ b/docs/NETWORK_ONLINE.md @@ -5,7 +5,7 @@ layout: default SPDX-License-Identifier: LGPL-2.1-or-later --- -# Network configuration synchronization points +# Network Configuration Synchronization Points systemd provides three target units related to network configuration: diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 6616448e905..1e3e6d8c3e3 100644 --- a/man/systemd.special.xml +++ b/man/systemd.special.xml @@ -500,21 +500,15 @@ sufficiently set up. What precisely this requires is left to the implementation of the network managing service. - Note the distinction between this unit and - network.target. This unit is an active - unit (i.e. pulled in by the consumer rather than the - provider of this functionality) and pulls in a service which - possibly adds substantial delays to further execution. In - contrast, network.target is a passive - unit (i.e. pulled in by the provider of the functionality, - rather than the consumer) that usually does not delay - execution much. Usually, network.target - is part of the boot of most systems, while - network-online.target is not, except - when at least one unit requires it. Also see Running - Services After the Network is up for more - information. + Note the distinction between this unit and network.target. This unit + is an active unit (i.e. pulled in by the consumer rather than the provider of this functionality) + and pulls in a service which possibly adds substantial delays to further execution. In contrast, + network.target is a passive unit (i.e. pulled in by the provider of the + functionality, rather than the consumer) that usually does not delay execution much. Usually, + network.target is part of the boot of most systems, while + network-online.target is not, except when at least one unit requires + it. Also see Running Services After the Network Is + Up for more information. All mount units for remote network file systems automatically pull in this unit, and order themselves after it. Note that networking daemons that simply provide @@ -991,8 +985,8 @@ will be stopped before the network — to whatever level it might be set up by then — is shut down. It is hence useful when writing service files that require network access on shutdown, which should order themselves after this target, but not pull it in. Also see Running Services After - the Network is up for more information. + url="https://systemd.io/NETWORK_ONLINE">Running Services After the Network Is Up for + more information. It must emphasized that at start-up there's no guarantee that hardware-based devices have @@ -1003,11 +997,11 @@ network-pre.target - This passive target unit may be pulled in by services - that want to run before any network is set up, for example - for the purpose of setting up a firewall. All network - management software orders itself after this target, but - does not pull it in. + This passive target unit may be pulled in by services that want to run before any network + is set up, for example for the purpose of setting up a firewall. All network management software + orders itself after this target, but does not pull it in. Also see Running Services After the Network Is Up for more + information.