From c592ebdf4f88acc378b093a9657e8aa357a380be Mon Sep 17 00:00:00 2001 From: Jan Engelhardt Date: Wed, 25 Dec 2024 17:07:17 +0100 Subject: [PATCH] man: grammar fixes for introductory adverbs/phrases --- man/bootctl.xml | 8 ++++---- man/crypttab.xml | 16 ++++++++-------- man/homectl.xml | 14 +++++++------- man/homed.conf.xml | 4 ++-- man/journalctl.xml | 6 +++--- man/journald.conf.xml | 2 +- man/kernel-command-line.xml | 4 ++-- man/kernel-install.xml | 6 +++--- man/logcontrol-example.c | 2 +- man/networkctl.xml | 4 ++-- man/org.freedesktop.resolve1.xml | 4 ++-- man/pam_systemd.xml | 2 +- man/portablectl.xml | 6 +++--- man/repart.d.xml | 10 +++++----- man/resolvectl.xml | 8 ++++---- man/resolved.conf.xml | 2 +- man/run0.xml | 4 ++-- man/sd_bus_add_match.xml | 2 +- man/sd_bus_attach_event.xml | 2 +- man/sd_bus_service_reconnect.c | 4 ++-- man/sd_bus_set_close_on_exit.xml | 2 +- man/sd_bus_set_sender.xml | 2 +- man/sd_bus_track_new.xml | 2 +- man/sd_event_add_child.xml | 6 +++--- man/sd_event_add_defer.xml | 2 +- man/sd_event_add_inotify.xml | 2 +- man/sd_event_add_io.xml | 4 ++-- man/sd_event_add_memory_pressure.xml | 2 +- man/sd_event_add_signal.xml | 2 +- man/sd_event_add_time.xml | 4 ++-- man/sd_event_set_signal_exit.xml | 2 +- man/sd_event_source_set_ratelimit.xml | 4 ++-- man/sd_journal_get_fd.xml | 2 +- man/sd_journal_has_runtime_files.xml | 4 ++-- man/standard-options.xml | 2 +- man/systemctl.xml | 4 ++-- man/systemd-ac-power.xml | 4 ++-- man/systemd-analyze.xml | 10 +++++----- man/systemd-bsod.service.xml | 2 +- man/systemd-creds.xml | 10 +++++----- man/systemd-cryptenroll.xml | 2 +- man/systemd-dissect.xml | 20 ++++++++++---------- man/systemd-firstboot.xml | 2 +- man/systemd-import-generator.xml | 2 +- man/systemd-journal-remote.service.xml | 2 +- man/systemd-journald.service.xml | 8 ++++---- man/systemd-measure.xml | 2 +- man/systemd-mount.xml | 8 ++++---- man/systemd-nspawn.xml | 10 +++++----- man/systemd-pcrlock.xml | 6 +++--- man/systemd-pcrphase.service.xml | 4 ++-- man/systemd-repart.xml | 14 +++++++------- man/systemd-resolved.service.xml | 2 +- man/systemd-run.xml | 2 +- man/systemd-sbsign.xml | 2 +- man/systemd-sleep.conf.xml | 2 +- man/systemd-soft-reboot.service.xml | 2 +- man/systemd-ssh-proxy.xml | 2 +- man/systemd-storagetm.service.xml | 2 +- man/systemd-sysext.xml | 2 +- man/systemd-system.conf.xml | 2 +- man/systemd-vmspawn.xml | 22 +++++++++++----------- man/systemd-vpick.xml | 4 ++-- man/systemd.exec.xml | 20 ++++++++++---------- man/systemd.generator.xml | 2 +- man/systemd.link.xml | 2 +- man/systemd.mount.xml | 2 +- man/systemd.netdev.xml | 4 ++-- man/systemd.network.xml | 10 +++++----- man/systemd.resource-control.xml | 8 ++++---- man/systemd.special.xml | 2 +- man/systemd.time.xml | 2 +- man/systemd.timer.xml | 2 +- man/systemd.unit.xml | 12 ++++++------ man/systemd.v.xml | 2 +- man/sysupdate.d.xml | 4 ++-- man/tmpfiles.d.xml | 4 ++-- man/userdbctl.xml | 6 +++--- man/varlinkctl.xml | 12 ++++++------ 79 files changed, 200 insertions(+), 200 deletions(-) diff --git a/man/bootctl.xml b/man/bootctl.xml index 3159f42347d..89ae019ad79 100644 --- a/man/bootctl.xml +++ b/man/bootctl.xml @@ -406,7 +406,7 @@ - By default the install command initializes a random seed file in + By default, the install command initializes a random seed file in the ESP. When creating an image it may be desirable to disable that in order to avoid having the same seed in all instances. @@ -468,8 +468,8 @@ os-release (e.g. vendorx-cashier-system). If set to (the default), the /etc/kernel/entry-token - file will be read if it exists, and the stored value used. Otherwise if the local machine ID is - initialized it is used. Otherwise IMAGE_ID= from os-release + file will be read if it exists, and the stored value used. Otherwise, if the local machine ID is + initialized it is used. Otherwise, IMAGE_ID= from os-release will be used, if set. Otherwise, ID= from os-release will be used, if set. @@ -509,7 +509,7 @@ Using the default entry name Linux Boot Manager is generally preferable as only one bootloader installed to a single ESP partition should be used to boot any number of OS installations found on the various disks installed in the system. Specifically distributions should not use this flag - to install a branded entry in the boot option list. However in situations with multiple disks, each with + to install a branded entry in the boot option list. However, in situations with multiple disks, each with their own ESP partition, it can be beneficial to make it easier to identify the bootloader being used in the firmware's boot option menu. diff --git a/man/crypttab.xml b/man/crypttab.xml index 7ef06c43599..ab77dea8373 100644 --- a/man/crypttab.xml +++ b/man/crypttab.xml @@ -104,7 +104,7 @@ see above and below. The key may be acquired via a PKCS#11 compatible hardware security token or - smartcard. In this case a saved key used in unlock process is stored on disk/removable media, acquired via + smartcard. In this case, a saved key used in unlock process is stored on disk/removable media, acquired via AF_UNIX, or stored in the LUKS2 JSON token metadata header. For RSA, the saved key is an encrypted volume key. The encrypted volume key is then decrypted by the PKCS#11 token with an RSA private key stored on it, and used to unlock the encrypted volume. For elliptic-curve (EC) cryptography, @@ -114,14 +114,14 @@ Similarly, the key may be acquired via a FIDO2 compatible hardware security token - (which must implement the "hmac-secret" extension). In this case a key generated randomly during + (which must implement the "hmac-secret" extension). In this case, a key generated randomly during enrollment is stored on disk/removable media, acquired via AF_UNIX, or stored in the LUKS2 JSON token metadata header. The random key is hashed via a keyed hash function (HMAC) on the FIDO2 token, using a secret key stored on the token that never leaves it. The resulting hash value is then used as key to unlock the encrypted volume. Use the option described below to use this mechanism. - Similarly, the key may be acquired via a TPM2 security chip. In this case a (during + Similarly, the key may be acquired via a TPM2 security chip. In this case, a (during enrollment) randomly generated key — encrypted by an asymmetric key derived from the TPM2 chip's seed key — is stored on disk/removable media, acquired via AF_UNIX, or stored in the LUKS2 JSON token metadata header. Use the option described below to use @@ -713,7 +713,7 @@ The specified URI can refer directly to a private key stored on a token or alternatively just to a slot or token, in which case a search for a suitable private key will be performed. In - this case if multiple suitable objects are found the token is refused. The keyfile configured + this case, if multiple suitable objects are found, the token is refused. The keyfile configured in the third column of the line is used as is (i.e. in binary form, unprocessed). The resulting decrypted key (for RSA) or derived shared secret (for ECC) is then Base64 encoded before it is used to unlock the LUKS volume. @@ -783,7 +783,7 @@ Takes a string, configuring the FIDO2 Relying Party (rp) for the FIDO2 unlock - operation. If not specified io.systemd.cryptsetup is used, except if the LUKS2 + operation. If not specified, io.systemd.cryptsetup is used, except if the LUKS2 JSON token header contains a different value. It should normally not be necessary to override this. @@ -891,7 +891,7 @@ public key specified at key enrollment time can be provided. See systemd-cryptenroll1 for details on enrolling TPM2 PCR public keys. If this option is not specified but it is attempted to - unlock a LUKS2 volume with a signed TPM2 PCR enrollment a suitable signature file + unlock a LUKS2 volume with a signed TPM2 PCR enrollment, a suitable signature file tpm2-pcr-signature.json is searched for in /etc/systemd/, /run/systemd/, /usr/lib/systemd/ (in this order). @@ -908,7 +908,7 @@ variants. See systemd-cryptenroll1 for details on enrolling TPM2 pcrlock policies. If this option is not specified but it is attempted - to unlock a LUKS2 volume with a TPM2 pcrlock enrollment a suitable signature file + to unlock a LUKS2 volume with a TPM2 pcrlock enrollment, a suitable signature file pcrlock.json is searched for in /run/systemd/ and /var/lib/systemd/ (in this order). @@ -934,7 +934,7 @@ Selects one or more TPM2 PCR banks to measure the volume key into, as configured with above. Multiple banks may be specified, separated by a colon - character. If not specified automatically determines available and used banks. Expects a message + character. If not specified, automatically determines available and used banks. Expects a message digest name (e.g. sha1, sha256, …) as argument, to identify the bank. diff --git a/man/homectl.xml b/man/homectl.xml index d4338c7f29b..4f251bb336c 100644 --- a/man/homectl.xml +++ b/man/homectl.xml @@ -261,7 +261,7 @@ Takes a path to use as home directory for the user. Note that this is the directory the user's home directory is mounted to while the user is logged in. This is not where the user's - data is actually stored, see for that. If not specified defaults to + data is actually stored, see for that. If not specified, defaults to /home/$USER. @@ -329,7 +329,7 @@ Takes a file system path to a directory. Specifies the skeleton directory to initialize the home directory with. All files and directories in the specified path are copied into - any newly create home directory. If not specified defaults to /etc/skel/. + any newly create home directory. If not specified, defaults to /etc/skel/. @@ -339,7 +339,7 @@ Takes a file system path. Specifies the shell binary to execute on terminal - logins. If not specified defaults to /bin/bash. + logins. If not specified, defaults to /bin/bash. @@ -633,7 +633,7 @@ After this time passes logging in may only proceed after the password is changed. specifies how much earlier than then the time configured with the user is warned at login to change their password as - it will expire soon. Finally configures the time which + it will expire soon. Finally, configures the time which has to pass after the password as expired until the user is not permitted to log in or change the password anymore. Note that these options only apply to password authentication, and do not apply to other forms of authentication, for example PKCS#11-based security token @@ -896,7 +896,7 @@ loopback file system instead of immediately from a common pool like the other backends do it). In regular intervals free disk space in the active home areas and their backing storage is redistributed among them, taking the weight value configured here into account. Expects an integer in the range - 1…10000, or the special string off. If not specified defaults to 100. The weight + 1…10000, or the special string off. If not specified, defaults to 100. The weight is used to scale free space made available to the home areas: a home area with a weight of 200 will get twice the free space as one with a weight of 100; a home area with a weight of 50 will get half of that. The backing file system will be assigned space for a weight of 20. If set to @@ -914,7 +914,7 @@ Configures the nosuid, nodev and - noexec mount options for the home directories. By default nodev + noexec mount options for the home directories. By default, nodev and nosuid are on, while noexec is off. For details about these mount options see mount8. @@ -932,7 +932,7 @@ directory/user account, as well as the file share ("service") to mount as directory. The latter is used when cifs storage is selected. The file share should be specified in format //host/share/directory/…. The - directory part is optional — if not specified the home directory will be placed in the top-level + directory part is optional — if not specified, the home directory will be placed in the top-level directory of the share. The setting allows specifying additional mount options when mounting the share, see mount.cifs8 diff --git a/man/homed.conf.xml b/man/homed.conf.xml index 4b51093877a..72d29fb43a6 100644 --- a/man/homed.conf.xml +++ b/man/homed.conf.xml @@ -60,7 +60,7 @@ homectl1. If not configured or assigned the empty string, the default storage is automatically determined: if not running in a container environment and /home/ is not itself encrypted, defaults - to luks. Otherwise defaults to subvolume if + to luks. Otherwise, defaults to subvolume if /home/ is on a btrfs file system, and directory otherwise. Note that the storage selected on the homectl command line always takes precedence. @@ -72,7 +72,7 @@ DefaultFileSystemType= When using luks as storage (see above), selects the default file system to use inside the user's LUKS volume. Takes one of btrfs, - ext4 or xfs. If not specified defaults to + ext4 or xfs. If not specified, defaults to btrfs. This setting has no effect if a different storage mechanism is used. The file system type selected on the homectl command line always takes precedence. diff --git a/man/journalctl.xml b/man/journalctl.xml index a21b4dc3c27..b977c7521ab 100644 --- a/man/journalctl.xml +++ b/man/journalctl.xml @@ -206,8 +206,8 @@ - Takes a journal namespace identifier string as argument. If not specified the data - collected by the default namespace is shown. If specified shows the log data of the specified + Takes a journal namespace identifier string as argument. If not specified, the data + collected by the default namespace is shown. If specified, shows the log data of the specified namespace instead. If the namespace is specified as * data from all namespaces is shown, interleaved. If the namespace identifier is prefixed with + data from the specified namespace and the default namespace is shown, interleaved, but no other. For details about @@ -272,7 +272,7 @@ If FILE exists and contains a cursor, start showing - entries after this location. Otherwise show entries according to the other + entries after this location. Otherwise, show entries according to the other given options. At the end, write the cursor of the last entry to FILE. Use this option to continually read the journal by sequentially calling journalctl. diff --git a/man/journald.conf.xml b/man/journald.conf.xml index 3aae53551c7..d96886baabe 100644 --- a/man/journald.conf.xml +++ b/man/journald.conf.xml @@ -487,7 +487,7 @@ Note that this option does not control whether systemd-journald collects generated audit records, it just controls whether it tells the kernel to generate them. If you need to prevent systemd-journald from collecting the generated messages, the socket - unit systemd-journald-audit.socket can be disabled and in this case this setting + unit systemd-journald-audit.socket can be disabled and, in this case, this setting is without effect. diff --git a/man/kernel-command-line.xml b/man/kernel-command-line.xml index 29d6426b01b..528f23b8093 100644 --- a/man/kernel-command-line.xml +++ b/man/kernel-command-line.xml @@ -168,7 +168,7 @@ the special value state. If false (the default), normal boot mode is selected, the root directory and /var/ are mounted as specified on the kernel command line or /etc/fstab, or otherwise configured. If true, full state-less boot mode is selected. In - this case the root directory is mounted as volatile memory file system (tmpfs), and only + this case, the root directory is mounted as volatile memory file system (tmpfs), and only /usr/ is mounted from the file system configured as root device, in read-only mode. This enables fully state-less boots were the vendor-supplied OS is used as shipped, with only default configuration and no stored state in effect, as /etc/ and /var/ (as @@ -403,7 +403,7 @@ If root= is not set (or set to gpt-auto) the automatic root partition discovery implemented by systemd-gpt-auto-generator8 - will be in effect. In this case rootfstype=, rootflags=, + will be in effect. In this case, rootfstype=, rootflags=, ro, rw will be interpreted by systemd-gpt-auto-generator. diff --git a/man/kernel-install.xml b/man/kernel-install.xml index 7f57d96839f..7c0ef0efc9f 100644 --- a/man/kernel-install.xml +++ b/man/kernel-install.xml @@ -308,9 +308,9 @@ If set to (the default), the /etc/kernel/entry-token (or $KERNEL_INSTALL_CONF_ROOT/entry-token) file will be read if it exists, and the - stored value used. Otherwise if the local machine ID is initialized it is used. Otherwise + stored value used. Otherwise, if the local machine ID is initialized, it is used. Otherwise, IMAGE_ID= from os-release will be used, if set. Otherwise, - ID= from os-release will be used, if set. Otherwise a + ID= from os-release will be used, if set. Otherwise, a randomly generated machine ID is used. Using the machine ID for naming the entries is generally preferable, however there are cases @@ -429,7 +429,7 @@ Note that while $KERNEL_INSTALL_ENTRY_TOKEN and $KERNEL_INSTALL_MACHINE_ID are often set to the same value, the latter is guaranteed to be a valid 32 character ID in lowercase hexadecimals while the former can be any short string. The - entry token to use is read from /etc/kernel/entry-token, if it exists. Otherwise a + entry token to use is read from /etc/kernel/entry-token, if it exists. Otherwise, a few possible candidates below $BOOT are checked for Boot Loader Specification Type 1 entry directories, and if found the entry token is derived from that. If that is not successful, $KERNEL_INSTALL_MACHINE_ID is used as fallback. diff --git a/man/logcontrol-example.c b/man/logcontrol-example.c index 23e73846cdb..eb527280ff9 100644 --- a/man/logcontrol-example.c +++ b/man/logcontrol-example.c @@ -220,7 +220,7 @@ int main(int argc, char **argv) { if (r < 0) return log_error(o.log_level, r, "sd_bus_add_object_vtable()"); - /* By default the service is assigned an ephemeral name. Also add a fixed + /* By default, the service is assigned an ephemeral name. Also add a fixed * one, so that clients know whom to call. * https://www.freedesktop.org/software/systemd/man/sd_bus_request_name.html */ diff --git a/man/networkctl.xml b/man/networkctl.xml index 86ef52915ea..c8ebaa227dd 100644 --- a/man/networkctl.xml +++ b/man/networkctl.xml @@ -296,7 +296,7 @@ Show discovered LLDP (Link Layer Discovery Protocol) neighbors. If one or more PATTERNs are specified only neighbors on those interfaces are shown. - Otherwise shows discovered neighbors on all interfaces. Note that for this feature to work, + Otherwise, shows discovered neighbors on all interfaces. Note that for this feature to work, LLDP= must be turned on for the specific interface, see systemd.network5 for details. @@ -632,7 +632,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR) drop-in directories are created and populated in one go. Multiple drop-ins may be "edited" in this mode with , and - the same contents will be written to all of them. Otherwise exactly one main configuration file + the same contents will be written to all of them. Otherwise, exactly one main configuration file is expected. diff --git a/man/org.freedesktop.resolve1.xml b/man/org.freedesktop.resolve1.xml index a9c121d12f5..324b6888537 100644 --- a/man/org.freedesktop.resolve1.xml +++ b/man/org.freedesktop.resolve1.xml @@ -500,7 +500,7 @@ node /org/freedesktop/resolve1 { hence where the data was found. The primary use cases for these five flags are follow-up look-ups based on DNS data retrieved - earlier. In this case it is often a good idea to limit the follow-up look-up to the protocol that was + earlier. In this case, it is often a good idea to limit the follow-up look-up to the protocol that was used to discover the first DNS result. The NO_CNAME flag controls whether CNAME/DNAME resource records shall be followed during the @@ -625,7 +625,7 @@ node /org/freedesktop/resolve1 { each non-existence proof. The secure counter is increased for each operation that successfully verified a signed reply, the insecure counter is increased for each operation that successfully verified that an unsigned reply is rightfully unsigned. The bogus counter is increased for each operation where the - validation did not check out and the data is likely to have been tempered with. Finally the + validation did not check out and the data is likely to have been tempered with. Finally, the indeterminate counter is increased for each operation which did not complete because the necessary keys could not be acquired or the cryptographic algorithms were unknown. diff --git a/man/pam_systemd.xml b/man/pam_systemd.xml index 183b37d676e..33d02c4efbc 100644 --- a/man/pam_systemd.xml +++ b/man/pam_systemd.xml @@ -192,7 +192,7 @@ for details on the capabilities concept. If not specified, the default bounding set is left as is (i.e. usually contains the full set of capabilities). The default ambient set is set to CAP_WAKE_ALARM for regular users if the PAM session is associated with a local - seat or if it is invoked for the systemd-user service. Otherwise defaults to the + seat or if it is invoked for the systemd-user service. Otherwise, defaults to the empty set. diff --git a/man/portablectl.xml b/man/portablectl.xml index 1cac9925570..5678171a170 100644 --- a/man/portablectl.xml +++ b/man/portablectl.xml @@ -119,7 +119,7 @@ /run/portables/, to make sure it is included in it. - By default all unit files whose names start with a prefix generated from the image's file name are copied + By default, all unit files whose names start with a prefix generated from the image's file name are copied out. Specifically, the prefix is determined from the image file name with any suffix such as .raw removed, truncated at the first occurrence of an underscore character (_), if there is one. The underscore logic is supposed to be used to versioning so that the @@ -186,7 +186,7 @@ Extracts various metadata from a portable service image and presents it to the caller. Specifically, the os-release5 file of the - image is retrieved as well as all matching unit files. By default a short summary showing the most relevant + image is retrieved as well as all matching unit files. By default, a short summary showing the most relevant metadata in combination with a list of matching unit files is shown (that is the unit files attach would install to the host system). If combined with (see above), the os-release data and the units files' contents is displayed unprocessed. This @@ -314,7 +314,7 @@ PROFILE - When attaching an image, select the profile to use. By default the default + When attaching an image, select the profile to use. By default, the default profile is used. For details about profiles, see below. diff --git a/man/repart.d.xml b/man/repart.d.xml index b5487e3b20c..8e3d496ab21 100644 --- a/man/repart.d.xml +++ b/man/repart.d.xml @@ -60,7 +60,7 @@ no matching partition file are left as they are. Note that these definitions may only be used to create and initialize new partitions or to grow - existing ones. In the latter case it will not grow the contained files systems however; separate + existing ones. In the latter case, it will not grow the contained files systems however; separate mechanisms, such as systemd-growfs8 may be used to grow the file systems inside of these partitions. Partitions may also be marked for automatic @@ -250,7 +250,7 @@ The textual label to assign to the partition if none is assigned yet. Note that this setting is not used for matching. It is also not used when a label is already set for an existing partition. It is thus only used when a partition is newly created or when an existing one had a no - label set (that is: an empty label). If not specified a label derived from the partition type is + label set (that is: an empty label). If not specified, a label derived from the partition type is automatically used. Simple specifier expansion is supported, see below. @@ -338,7 +338,7 @@ SizeMaxBytes=) otherwise. If the backing device does not provide enough space to fulfill the constraints placing the partition will fail. For partitions that shall be created, depending on the setting of Priority= (see above) the partition might be dropped - and the placing algorithm restarted. By default a minimum size constraint of 10M and no maximum size + and the placing algorithm restarted. By default, a minimum size constraint of 10M and no maximum size constraint is set. @@ -351,7 +351,7 @@ Specifies minimum and maximum size constraints in bytes for the free space after the partition (the "padding"). Semantics are similar to SizeMinBytes= and SizeMaxBytes=, except that unlike partition sizes free space can be shrunk and can - be as small as zero. By default no size constraints on padding are set, so that only + be as small as zero. By default, no size constraints on padding are set, so that only PaddingWeight= determines the size of the padding applied. @@ -718,7 +718,7 @@ Flags= Configures the 64-bit GPT partition flags field to set for the partition when creating - it. This option has no effect if the partition already exists. If not specified the flags values is + it. This option has no effect if the partition already exists. If not specified, the flags value is set to all zeroes, except for the three bits that can also be configured via NoAuto=, ReadOnly= and GrowFileSystem=; see below for details on the defaults for these three flags. Specify the flags value in hexadecimal (by diff --git a/man/resolvectl.xml b/man/resolvectl.xml index 4e3b35a330e..a176fe4fa82 100644 --- a/man/resolvectl.xml +++ b/man/resolvectl.xml @@ -43,7 +43,7 @@ The program's output contains information about the protocol used for the look-up and on which network interface the data was discovered. It also contains information on whether the information could be - authenticated. All data for which local DNSSEC validation succeeds is considered authenticated. Moreover all data + authenticated. All data for which local DNSSEC validation succeeds is considered authenticated. Moreover, all data originating from local, trusted sources is also reported authenticated, including resolution of the local host name, the localhost hostname or all data from /etc/hosts. @@ -84,10 +84,10 @@ RFC 2782 SRV services, depending on the specified list of parameters. If three parameters are passed the first is assumed to be the DNS-SD service name, the second the SRV service type, and the third the - domain to search in. In this case a full DNS-SD style SRV and + domain to search in. In this case, a full DNS-SD style SRV and TXT lookup is executed. If only two parameters are specified, the first is assumed to be the SRV service type, and the second the - domain to look in. In this case no TXT resource record is requested. + domain to look in. In this case, no TXT resource record is requested. Finally, if only one parameter is specified, it is assumed to be a domain name, that is already prefixed with an SRV type, and an SRV lookup is done (no TXT). @@ -298,7 +298,7 @@ llmnr-ipv4, llmnr-ipv6 (LLMNR via the indicated underlying IP protocols), mdns (Multicast DNS), mdns-ipv4, mdns-ipv6 (MDNS via the indicated underlying IP protocols). - By default the lookup is done via all protocols suitable for the lookup. If used, limits the set of + By default, the lookup is done via all protocols suitable for the lookup. If used, limits the set of protocols that may be used. Use this option multiple times to enable resolving via multiple protocols at the same time. The setting llmnr is identical to specifying this switch once with llmnr-ipv4 and once via llmnr-ipv6. Note that this option does not force diff --git a/man/resolved.conf.xml b/man/resolved.conf.xml index 73f73c3b5d9..a90de83b848 100644 --- a/man/resolved.conf.xml +++ b/man/resolved.conf.xml @@ -201,7 +201,7 @@ returned data could not be verified (either because the data was found unsigned in the DNS, or the DNS server did not support DNSSEC or no appropriate trust anchors were known). In - the latter case it is assumed that client programs employ a + the latter case, it is assumed that client programs employ a secondary scheme to validate the returned DNS data, should this be required. diff --git a/man/run0.xml b/man/run0.xml index 1c42d46baa9..16774813d48 100644 --- a/man/run0.xml +++ b/man/run0.xml @@ -215,7 +215,7 @@ Set a shell prompt prefix string. This ultimately controls the $SHELL_PROMPT_PREFIX environment variable for the invoked program, which is - typically imported into the shell prompt. By default – if emojis are supported – a superhero emoji is + typically imported into the shell prompt. By default – if emojis are supported –, a superhero emoji is shown (🦸). This default may also be changed (or turned off) by passing the $SYSTEMD_RUN_SHELL_PROMPT_PREFIX environment variable to run0, see below. Set to an empty string to disable shell prompt prefixing. @@ -291,7 +291,7 @@ $SHELL_PROMPT_PREFIX - By default set to the superhero emoji (if supported), but may be overridden with the + By default, set to the superhero emoji (if supported), but may be overridden with the $SYSTEMD_RUN_SHELL_PROMPT_PREFIX environment variable (see below), or the switch (see above). diff --git a/man/sd_bus_add_match.xml b/man/sd_bus_add_match.xml index 575d628364c..2cdd6db055d 100644 --- a/man/sd_bus_add_match.xml +++ b/man/sd_bus_add_match.xml @@ -134,7 +134,7 @@ If an error occurs during the callback invocation, the callback should return a negative error number (optionally, a more precise error may be returned in ret_error, as well). If it wants other - callbacks that match the same rule to be called, it should return 0. Otherwise it should return a positive integer. + callbacks that match the same rule to be called, it should return 0. Otherwise, it should return a positive integer. If the bus refers to a direct connection (i.e. not a bus connection, as set with diff --git a/man/sd_bus_attach_event.xml b/man/sd_bus_attach_event.xml index 16d46e5c45d..47baedc2392 100644 --- a/man/sd_bus_attach_event.xml +++ b/man/sd_bus_attach_event.xml @@ -58,7 +58,7 @@ will be automatically read and processed, and outgoing messages written, whenever the event loop is run. When the event loop is about to terminate, the bus connection is automatically flushed and closed (see sd_bus_set_close_on_exit3 for - details on this). By default bus connection objects are not attached to any event loop. When a bus connection + details on this). By default, bus connection objects are not attached to any event loop. When a bus connection object is attached to one it is not necessary to invoke sd_bus_wait3 or sd_bus_process3 as this diff --git a/man/sd_bus_service_reconnect.c b/man/sd_bus_service_reconnect.c index fc7c3b1a724..ddb9c6b4970 100644 --- a/man/sd_bus_service_reconnect.c +++ b/man/sd_bus_service_reconnect.c @@ -181,7 +181,7 @@ static int setup(object *o) { o); if (r < 0) return log_error(r, "sd_bus_add_object_vtable()"); - /* By default the service is only assigned an ephemeral name. Also add a + /* By default, the service is only assigned an ephemeral name. Also add a * well-known one, so that clients know whom to call. This needs to be * asynchronous, as D-Bus might not be yet available. The callback will check * whether the error is expected or not, in case it fails. @@ -242,7 +242,7 @@ int main(int argc, char **argv) { if (r < 0) return log_error(r, "sd_event_default()"); - /* By default the event loop will terminate when all sources have disappeared, + /* By default, the event loop will terminate when all sources have disappeared, * so we have to keep it 'occupied'. Register signal handling to do so. * https://www.freedesktop.org/software/systemd/man/sd_event_add_signal.html */ diff --git a/man/sd_bus_set_close_on_exit.xml b/man/sd_bus_set_close_on_exit.xml index 43f6eff093f..bb551a0105c 100644 --- a/man/sd_bus_set_close_on_exit.xml +++ b/man/sd_bus_set_close_on_exit.xml @@ -55,7 +55,7 @@ sd-event3 event loop, see sd_bus_attach_event3. - By default this mechanism is enabled and makes sure that any pending messages that have not been + By default, this mechanism is enabled and makes sure that any pending messages that have not been written to the bus connection are written out when the event loop is shutting down. In some cases this behaviour is not desirable, for example when the bus connection shall remain usable until after the event loop exited. If b is true, the feature is enabled diff --git a/man/sd_bus_set_sender.xml b/man/sd_bus_set_sender.xml index 0f8e40d3a6a..24108446a0e 100644 --- a/man/sd_bus_set_sender.xml +++ b/man/sd_bus_set_sender.xml @@ -50,7 +50,7 @@ that are sent on the connection and have no sender set yet, for example through sd_bus_message_set_sender3. Note that this function is only supported on direct connections, i.e. not on connections to a bus broker as the broker - will fill in the sender service name automatically anyway. By default no sender name is configured, and hence + will fill in the sender service name automatically anyway. By default, no sender name is configured, and hence messages are sent without sender field set. If the name parameter is specified as NULL the default sender service name is cleared, returning to the default state if a default sender service name was set before. If passed as non-NULL the specified name must be a valid diff --git a/man/sd_bus_track_new.xml b/man/sd_bus_track_new.xml index 7041e92f786..e8480eb52e7 100644 --- a/man/sd_bus_track_new.xml +++ b/man/sd_bus_track_new.xml @@ -137,7 +137,7 @@ irrelevant and the tracking of the specific peer is immediately removed. sd_bus_track_get_recursive() may be used to determine whether the bus peer tracking object is operating in recursive mode. sd_bus_track_set_recursive() may be used to enable or - disable recursive mode. By default a bus peer tracking object operates in non-recursive mode, and + disable recursive mode. By default, a bus peer tracking object operates in non-recursive mode, and sd_bus_track_get_recursive() for a newly allocated object hence returns a value equal to zero. Use sd_bus_track_set_recursive() to enable recursive mode, right after allocation. It takes a boolean argument to enable or disable recursive mode. Note that tracking objects for which diff --git a/man/sd_event_add_child.xml b/man/sd_event_add_child.xml index 36b83e6f07a..e3b9cdd7460 100644 --- a/man/sd_event_add_child.xml +++ b/man/sd_event_add_child.xml @@ -155,7 +155,7 @@ project='man-pages'>pthread_sigmask3). If the second parameter of sd_event_add_child() is passed as - NULL no reference to the event source object is returned. In this case the event + NULL no reference to the event source object is returned. In this case, the event source is considered "floating", and will be destroyed implicitly when the event loop itself is destroyed. @@ -212,7 +212,7 @@ sd_event_source_get_child_pidfd_own() may be used to query whether the pidfd the event source encapsulates shall be closed when the event source is freed. This function returns zero - if the pidfd shall be left open, and positive if it shall be closed automatically. By default this + if the pidfd shall be left open, and positive if it shall be closed automatically. By default, this setting defaults to on if the event source was allocated via sd_event_add_child() and off if it was allocated via sd_event_add_child_pidfd(). The sd_event_source_set_child_pidfd_own() function may be used to change the setting and @@ -221,7 +221,7 @@ sd_event_source_get_child_process_own() may be used to query whether the process the event source watches shall be killed (with SIGKILL) and reaped when the event source is freed. This function returns zero if the process shell be left running, and positive if - it shall be killed and reaped automatically. By default this setting defaults to off. The + it shall be killed and reaped automatically. By default, this setting defaults to off. The sd_event_source_set_child_process_own() function may be used to change the setting and takes a boolean parameter with the new setting. Note that currently if the calling process is terminated abnormally the watched process might survive even thought the event source ceases to diff --git a/man/sd_event_add_defer.xml b/man/sd_event_add_defer.xml index af43ef14495..811992453b4 100644 --- a/man/sd_event_add_defer.xml +++ b/man/sd_event_add_defer.xml @@ -122,7 +122,7 @@ sd_event_source_set_enabled3. If the second parameter of these functions is passed as NULL no reference to - the event source object is returned. In this case the event source is considered "floating", and will be + the event source object is returned. In this case, the event source is considered "floating", and will be destroyed implicitly when the event loop itself is destroyed. If the handler parameter to sd_event_add_defer() or diff --git a/man/sd_event_add_inotify.xml b/man/sd_event_add_inotify.xml index ed26c8ac96e..abebff32f8b 100644 --- a/man/sd_event_add_inotify.xml +++ b/man/sd_event_add_inotify.xml @@ -126,7 +126,7 @@ sd_event_source_set_enabled3. If the second parameter of sd_event_add_inotify() is passed as - NULL no reference to the event source object is returned. In this case the event + NULL no reference to the event source object is returned. In this case, the event source is considered "floating", and will be destroyed implicitly when the event loop itself is destroyed. diff --git a/man/sd_event_add_io.xml b/man/sd_event_add_io.xml index 0a53221b844..baf1debaf04 100644 --- a/man/sd_event_add_io.xml +++ b/man/sd_event_add_io.xml @@ -156,7 +156,7 @@ If the second parameter of sd_event_add_io() is NULL no reference to the event source object - is returned. In this case the event source is considered + is returned. In this case, the event source is considered "floating", and will be destroyed implicitly when the event loop itself is destroyed. @@ -227,7 +227,7 @@ event source shall take ownership of the file descriptor. Takes a boolean parameter b. When true (nonzero), the file descriptor will be closed automatically when the event source is freed or when the file descriptor is replaced by - sd_event_source_set_io_fd(). By default the descriptor is not owned by the event + sd_event_source_set_io_fd(). By default, the descriptor is not owned by the event source, and the application has to do close it on its own if needed. sd_event_source_get_io_fd_own() may be used to query the current setting of the file diff --git a/man/sd_event_add_memory_pressure.xml b/man/sd_event_add_memory_pressure.xml index ba7502a466f..6b24643f417 100644 --- a/man/sd_event_add_memory_pressure.xml +++ b/man/sd_event_add_memory_pressure.xml @@ -84,7 +84,7 @@ with SD_EVENT_OFF. If the second parameter of sd_event_add_memory_pressure() is - NULL no reference to the event source object is returned. In this case the event + NULL no reference to the event source object is returned. In this case, the event source is considered "floating", and will be destroyed implicitly when the event loop itself is destroyed. diff --git a/man/sd_event_add_signal.xml b/man/sd_event_add_signal.xml index ec8210b0b80..1956f45f6e1 100644 --- a/man/sd_event_add_signal.xml +++ b/man/sd_event_add_signal.xml @@ -107,7 +107,7 @@ If the second parameter of sd_event_add_signal() is NULL no reference to the event source object - is returned. In this case the event source is considered + is returned. In this case, the event source is considered "floating", and will be destroyed implicitly when the event loop itself is destroyed. diff --git a/man/sd_event_add_time.xml b/man/sd_event_add_time.xml index c65c367eacc..75176c06d25 100644 --- a/man/sd_event_add_time.xml +++ b/man/sd_event_add_time.xml @@ -164,7 +164,7 @@ If the second parameter of sd_event_add_time() is NULL no reference to the event source object - is returned. In this case the event source is considered + is returned. In this case, the event source is considered "floating", and will be destroyed implicitly when the event loop itself is destroyed. @@ -197,7 +197,7 @@ base the usec parameter passed to the timer callback, or the timestamp returned by sd_event_now(). In the former case timer - events will be regular, while in the latter case the scheduling + events will be regular, while in the latter case, the scheduling latency will keep accumulating on the timer. sd_event_source_get_time() retrieves the configured time value of an event diff --git a/man/sd_event_set_signal_exit.xml b/man/sd_event_set_signal_exit.xml index 0ee04702f59..fd40863868b 100644 --- a/man/sd_event_set_signal_exit.xml +++ b/man/sd_event_set_signal_exit.xml @@ -48,7 +48,7 @@ If the parameter b is specified as true, the event loop will terminate on SIGINT and SIGTERM. If specified as false, it will no longer. When this functionality is turned off the calling thread's signal mask is restored to match the - state before it was turned on, for the two signals. By default the two signals are not handled by the + state before it was turned on, for the two signals. By default, the two signals are not handled by the event loop, and Linux' default signal handling for them is in effect. It is customary for UNIX programs to exit on either of these two signals, hence it is typically a diff --git a/man/sd_event_source_set_ratelimit.xml b/man/sd_event_source_set_ratelimit.xml index ba30fea69af..4adfb44f73e 100644 --- a/man/sd_event_source_set_ratelimit.xml +++ b/man/sd_event_source_set_ratelimit.xml @@ -74,10 +74,10 @@ dispatched more often than the specified burst within the specified interval it is placed in a mode similar to being disabled with sd_event_source_set_enabled3 - and the SD_EVENT_OFF parameter. However it is disabled only temporarily – once the + and the SD_EVENT_OFF parameter. However, it is disabled only temporarily – once the specified interval is over regular operation resumes. It is again disabled temporarily once the specified rate limiting is hit the next time. If either the interval or the burst value are specified as zero, rate - limiting is turned off. By default event sources do not have rate limiting enabled. Note that rate + limiting is turned off. By default, event sources do not have rate limiting enabled. Note that rate limiting and disabling via sd_event_source_set_enabled() are independent of each other, and an event source will only effect event loop wake-ups and is dispatched while it both is enabled and rate limiting is not in effect. diff --git a/man/sd_journal_get_fd.xml b/man/sd_journal_get_fd.xml index 2f7afa87630..9510ecc45f8 100644 --- a/man/sd_journal_get_fd.xml +++ b/man/sd_journal_get_fd.xml @@ -192,7 +192,7 @@ else { invocation. If SD_JOURNAL_APPEND is returned, new entries have been appended to the end - of the journal. In this case it is sufficient to simply continue reading at the previous end location of the + of the journal. In this case, it is sufficient to simply continue reading at the previous end location of the journal, to read the newly added entries. If SD_JOURNAL_INVALIDATE, journal files were added to or removed from the diff --git a/man/sd_journal_has_runtime_files.xml b/man/sd_journal_has_runtime_files.xml index dd6fc02d583..a2dcc1c05f2 100644 --- a/man/sd_journal_has_runtime_files.xml +++ b/man/sd_journal_has_runtime_files.xml @@ -46,11 +46,11 @@ sd_journal_has_runtime_files() returns a positive value if runtime journal files (present in /run/systemd/journal/) have been found. - Otherwise returns 0. + Otherwise, returns 0. sd_journal_has_persistent_files() returns a positive value if persistent journal files (present in /var/log/journal/) have been found. - Otherwise returns 0. + Otherwise, returns 0. diff --git a/man/standard-options.xml b/man/standard-options.xml index d181f90b837..1e958594ad9 100644 --- a/man/standard-options.xml +++ b/man/standard-options.xml @@ -110,7 +110,7 @@ Takes an image policy string as argument, as per systemd.image-policy7. The policy is enforced when operating on the disk image specified via , see - above. If not specified defaults to the * policy, i.e. all recognized file systems + above. If not specified, defaults to the * policy, i.e. all recognized file systems in the image are used. diff --git a/man/systemctl.xml b/man/systemctl.xml index 336ac815f81..770f0e0c041 100644 --- a/man/systemctl.xml +++ b/man/systemctl.xml @@ -59,7 +59,7 @@ List units that systemd currently has in memory. This includes units that are either referenced directly or through a dependency, units that are pinned by applications programmatically, - or units that were active in the past and have failed. By default only units which are active, have pending + or units that were active in the past and have failed. By default, only units which are active, have pending jobs, or have failed are shown; this can be changed with option . If one or more PATTERNs are specified, only units matching one of them are shown. The units that are shown are additionally filtered by and if those @@ -1108,7 +1108,7 @@ Jan 12 10:46:45 example.com bluetoothd[8900]: gatt-time-server: Input/output err bad - The unit file is invalid or another error occurred. Note that is-enabled will not actually return this state, but print an error message instead. However the unit file listing printed by list-unit-files might show it. + The unit file is invalid or another error occurred. Note that is-enabled will not actually return this state, but print an error message instead. However, the unit file listing printed by list-unit-files might show it. > 0 diff --git a/man/systemd-ac-power.xml b/man/systemd-ac-power.xml index a693187864d..ca4aa4d768d 100644 --- a/man/systemd-ac-power.xml +++ b/man/systemd-ac-power.xml @@ -31,7 +31,7 @@ Description systemd-ac-power may be used to check whether the system - is running on AC power or not. By default it will simply return success (if we + is running on AC power or not. By default, it will simply return success (if we can detect that we are running on AC power) or failure, with no output. This can be useful for example to debug ConditionACPower= (see systemd.unit5). @@ -55,7 +55,7 @@ - Instead of showing AC power state, show low battery state. In this case will return + Instead of showing AC power state, show low battery state. In this case, will return zero if all batteries are currently discharging and below 5% of maximum charge. Returns non-zero otherwise. diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml index 1ccef877b1c..a371810f268 100644 --- a/man/systemd-analyze.xml +++ b/man/systemd-analyze.xml @@ -291,7 +291,7 @@ multi-user.target reached after 47.820s in userspace blame command, this only takes into account the time units spent in activating state, and hence does not cover units that never went through an activating state (such as device units that transition directly from - inactive to active). Moreover it does not show information on + inactive to active). Moreover, it does not show information on jobs (and in particular not jobs that timed out). @@ -688,7 +688,7 @@ NAutoVTs=8 This command has two distinct modes of operation, depending on whether the operator OP is specified. - In the first mode — when OP is not specified — it will compare the two + In the first mode — when OP is not specified —, it will compare the two version strings and print either VERSION1 < VERSION2, or VERSION1 == VERSION2, or VERSION1 > @@ -964,7 +964,7 @@ default ignore - - Reports whether the system is equipped with a usable TPM2 device. If a TPM2 device has been discovered, is supported, and is being used by firmware, by the OS kernel drivers and by userspace (i.e. systemd) this prints yes and exits with exit status zero. If no such device is - discovered/supported/used, prints no. Otherwise prints + discovered/supported/used, prints no. Otherwise, prints partial. In either of these two cases exits with non-zero exit status. It also shows five lines indicating separately whether firmware, drivers, the system, the kernel and libraries discovered/support/use TPM2. Currently, required libraries are libtss2-esys.so.0, @@ -1630,7 +1630,7 @@ LEGEND: M → sys_vendor (LENOVO) ┄ F → product_family (ThinkPad X1 Carbon G When used with the calendar command, show next iterations relative - to the specified point in time. If not specified defaults to the current time. + to the specified point in time. If not specified, defaults to the current time. @@ -1730,7 +1730,7 @@ LEGEND: M → sys_vendor (LENOVO) ┄ F → product_family (ThinkPad X1 Carbon G 0 or 1 if the condition is respectively true or false. In case of the has-tpm2 command returns 0 if a TPM2 device is discovered, - supported and used by firmware, driver, and userspace (i.e. systemd). Otherwise returns the OR + supported and used by firmware, driver, and userspace (i.e. systemd). Otherwise, returns the OR combination of the value 1 (in case firmware support is missing), 2 (in case driver support is missing) and 4 (in case userspace support is missing). If no TPM2 support is available at all, value 7 is hence returned. diff --git a/man/systemd-bsod.service.xml b/man/systemd-bsod.service.xml index f9812fb6627..ad16b69eaa5 100644 --- a/man/systemd-bsod.service.xml +++ b/man/systemd-bsod.service.xml @@ -60,7 +60,7 @@ - Specify the TTY to output to. By default systemd-bsod will + Specify the TTY to output to. By default, systemd-bsod will automatically find a free VT to display the message on. If this option is specified a TTY may be selected explicitly. Use to direct output to the terminal the command is invoked on. diff --git a/man/systemd-creds.xml b/man/systemd-creds.xml index a9ef14226fd..55c5064b65a 100644 --- a/man/systemd-creds.xml +++ b/man/systemd-creds.xml @@ -271,13 +271,13 @@ When specified with the encrypt command controls the credential - name to embed in the encrypted credential data. If not specified the name is chosen automatically + name to embed in the encrypted credential data. If not specified, the name is chosen automatically from the filename component of the specified output path. If specified as empty string no credential name is embedded in the encrypted credential, and no verification of credential name is done when the credential is decrypted. When specified with the decrypt command control the credential name to - validate the credential name embedded in the encrypted credential with. If not specified the name is + validate the credential name embedded in the encrypted credential with. If not specified, the name is chosen automatically from the filename component of the specified input path. If no credential name is embedded in the encrypted credential file (i.e. the with an empty string was used when encrypted) the specified name has no effect as no credential name validation is @@ -300,7 +300,7 @@ When specified with the decrypt command controls the timestamp to use to validate the "not-after" timestamp that was configured with during - encryption. If not specified defaults to the current system time. + encryption. If not specified, defaults to the current system time. @@ -311,7 +311,7 @@ When specified with the encrypt command controls the time when the credential shall not be used anymore. This embeds the specified timestamp in the encrypted credential. During decryption the timestamp is checked against the current system clock, and if the - timestamp is in the past the decryption will fail. By default no such timestamp is set. Takes a + timestamp is in the past the decryption will fail. By default, no such timestamp is set. Takes a timestamp specification in the format described in systemd.time7. @@ -392,7 +392,7 @@ /etc/systemd/, /run/systemd/, /usr/lib/systemd/ (searched in this order), it is automatically used. The option takes a list of TPM2 PCR indexes to bind to (same - syntax as described above). If not specified defaults to 11 (i.e. this + syntax as described above). If not specified, defaults to 11 (i.e. this binds the policy to any unified kernel image for which a PCR signature can be provided). Note the difference between and diff --git a/man/systemd-cryptenroll.xml b/man/systemd-cryptenroll.xml index 949e07fd632..b80a63f4266 100644 --- a/man/systemd-cryptenroll.xml +++ b/man/systemd-cryptenroll.xml @@ -628,7 +628,7 @@ /etc/systemd/, /run/systemd/, /usr/lib/systemd/ (searched in this order), it is automatically used. The option takes a list of TPM2 PCR indexes to bind to (same - syntax as described above). If not specified defaults to 11 (i.e. this + syntax as described above). If not specified, defaults to 11 (i.e. this binds the policy to any unified kernel image for which a PCR signature can be provided). Note the difference between and diff --git a/man/systemd-dissect.xml b/man/systemd-dissect.xml index 191ae3394bb..fccc61c6d8d 100644 --- a/man/systemd-dissect.xml +++ b/man/systemd-dissect.xml @@ -152,7 +152,7 @@ unmounted. The OS image may either be specified as path to an OS image stored in a regular file or may - refer to block device node (in the latter case the block device must be the "whole" device, i.e. not + refer to block device node (in the latter case, the block device must be the "whole" device, i.e. not a partition device). (The other supported commands described here support this, too.) All mounted file systems are checked with the appropriate Detach the specified disk image from a loopback block device. This undoes the effect of above. This expects either a path to a loopback block device as an - argument, or the path to the backing image file. In the latter case it will automatically determine + argument, or the path to the backing image file. In the latter case, it will automatically determine the right device to detach. @@ -277,9 +277,9 @@ the current working directory, or an absolute path, both outside of the image). If the destination path is omitted or specified as dash (-), the specified file is written to standard output. If the source path in the image file system refers to a regular file it is copied to - the destination path. In this case access mode, extended attributes and timestamps are copied as + the destination path. In this case, access mode, extended attributes and timestamps are copied as well, but file ownership is not. If the source path in the image refers to a directory, it is copied - to the destination path, recursively with all containing files and directories. In this case the file + to the destination path, recursively with all containing files and directories. In this case, the file ownership is copied too. @@ -295,9 +295,9 @@ image) and a destination path (relative to the image's root directory). If the source path is omitted or specified as dash (-), the data to write is read from standard input. If the source path in the host file system refers to a regular file, it is copied to the destination path. - In this case access mode, extended attributes and timestamps are copied as well, but file ownership + In this case, access mode, extended attributes and timestamps are copied as well, but file ownership is not. If the source path in the host file system refers to a directory it is copied to the - destination path, recursively with all containing files and directories. In this case the file + destination path, recursively with all containing files and directories. In this case, the file ownership is copied too. As with file system checks are implicitly run before the copy @@ -344,7 +344,7 @@ dissection policy into account. Since this operation does not mount file systems, this command – unlike all other commands implemented by this tool – requires no privileges other than the ability to access the specified file. Prints "OK" and returns zero if the image appears to be in order and - matches the specified image dissection policy. Otherwise prints an error message and returns + matches the specified image dissection policy. Otherwise, prints an error message and returns non-zero. @@ -366,7 +366,7 @@ - Operate in read-only mode. By default will establish + Operate in read-only mode. By default, will establish writable mount points. If this option is specified they are established in read-only mode instead. @@ -376,7 +376,7 @@ - Turn off automatic file system checking. By default when an image is accessed for + Turn off automatic file system checking. By default, when an image is accessed for writing (by or ) the file systems contained in the OS image are automatically checked using the appropriate fsck8 @@ -390,7 +390,7 @@ Turn off automatic growing of accessed file systems to their partition size, if - marked for that in the GPT partition table. By default when an image is accessed for writing (by + marked for that in the GPT partition table. By default, when an image is accessed for writing (by or ) the file systems contained in the OS image are automatically grown to their partition sizes, if bit 59 in the GPT partition flags is set for partition types that are defined by the - Takes a boolean argument. By default when prompting the user for configuration + Takes a boolean argument. By default, when prompting the user for configuration options a brief welcome text is shown before the first question is asked. Pass false to this option to turn off the welcome text. diff --git a/man/systemd-import-generator.xml b/man/systemd-import-generator.xml index 108509d7d46..1ccccb26894 100644 --- a/man/systemd-import-generator.xml +++ b/man/systemd-import-generator.xml @@ -130,7 +130,7 @@ completing the download successfully, or unsuccessfully. See SuccessAction=/FailureAction= on systemd.unit5 for - details about the available actions. If not specified no action is taken, and the system will + details about the available actions. If not specified, no action is taken, and the system will continue to boot normally. diff --git a/man/systemd-journal-remote.service.xml b/man/systemd-journal-remote.service.xml index be195a05086..d6258ce2fcd 100644 --- a/man/systemd-journal-remote.service.xml +++ b/man/systemd-journal-remote.service.xml @@ -49,7 +49,7 @@ systemd-journal-remote.service is a system service that uses systemd-journal-remote to listen for connections. systemd-journal-remote.socket configures the network address that - systemd-journal-remote.service listens on. By default this is port 19532. + systemd-journal-remote.service listens on. By default, this is port 19532. What connections are accepted and how the received data is stored can be configured through the journal-remote.conf5 configuration file. diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index 94df62fb500..3a9d8049725 100644 --- a/man/systemd-journald.service.xml +++ b/man/systemd-journald.service.xml @@ -77,7 +77,7 @@ necessary. Individual fields making up a log record stored in the journal may be up to 2⁶⁴-1 bytes in size. The journal service stores log data either persistently below /var/log/journal or in a - volatile way below /run/log/journal/ (in the latter case it is lost at reboot). By default, log + volatile way below /run/log/journal/ (in the latter case, it is lost at reboot). By default, log data is stored persistently if /var/log/journal/ exists during boot, with an implicit fallback to volatile storage otherwise. Use Storage= in journald.conf5 to configure @@ -112,7 +112,7 @@ systemd-tmpfiles --create --prefix /var/log/journal If systemd-journald.service is stopped, the stream connections associated with all services are terminated. Further writes to those streams by the service will result in EPIPE - errors. In order to react gracefully in this case it is recommended that programs logging to standard output/error + errors. In order to react gracefully in this case, it is recommended that programs logging to standard output/error ignore such errors. If the SIGPIPE UNIX signal handler is not blocked or turned off, such write attempts will also result in such process signals being generated, see signal7. @@ -152,7 +152,7 @@ systemd-tmpfiles --create --prefix /var/log/journal consisting of one or more services from the rest of the system and a mechanism for improving performance. Multiple journal namespaces may exist simultaneously, each defining its own, independent log stream managed by its own instance of systemd-journald. Namespaces are independent of - each other, both in the data store and in the IPC interface. By default only a single 'default' namespace + each other, both in the data store and in the IPC interface. By default, only a single "default namespace exists, managed by systemd-journald.service (and its associated socket units). Additional namespaces are created by starting an instance of the systemd-journald@.service service template. The instance name is the namespace @@ -169,7 +169,7 @@ systemd-tmpfiles --create --prefix /var/log/journal the native logging protocol of the journal and via stdout/stderr; the logging from all three transports is associated with the namespace. - By default only the default namespace will collect kernel and audit log messages. + By default, only the default namespace will collect kernel and audit log messages. The systemd-journald instance of the default namespace is configured through /etc/systemd/journald.conf (see below), while the other instances are configured diff --git a/man/systemd-measure.xml b/man/systemd-measure.xml index 408e89ec804..97f1abe1f9f 100644 --- a/man/systemd-measure.xml +++ b/man/systemd-measure.xml @@ -178,7 +178,7 @@ same PEM key should be supplied in both cases. If the is not specified but is - specified the public key is automatically derived from the private key. + specified, the public key is automatically derived from the private key. can be used to specify an X.509 certificate as an alternative to since v256. diff --git a/man/systemd-mount.xml b/man/systemd-mount.xml index 60b10ec18e4..d0eb9678d7f 100644 --- a/man/systemd-mount.xml +++ b/man/systemd-mount.xml @@ -138,7 +138,7 @@ Enable probing of the mount source. This switch is implied if a single argument is specified on the command line. If passed, additional metadata is read from the device to enhance the unit to create. For example, a descriptive string for the transient units is generated from the file system label and device - model. Moreover if a removable block device (e.g. USB stick) is detected an automount unit instead of a regular + model. Moreover, if a removable block device (e.g. USB stick) is detected an automount unit instead of a regular mount unit is created, with a short idle timeout, in order to ensure the file-system is placed in a clean state quickly after each access. @@ -218,7 +218,7 @@ accessed. In automount mode the switch (see below) may be used to ensure the mount point is unmounted automatically after the last access and an idle period passed. - If this switch is not specified it defaults to false. If not specified and is + If this switch is not specified, it defaults to false. If not specified and is used (or only a single argument passed, which implies , see above), and the file system block device is detected to be removable, it is set to true, in order to increase the chance that the file system is in a fully clean state if the device is unplugged abruptly. @@ -238,7 +238,7 @@ Takes a time value that controls the idle timeout in automount mode. If set to - infinity (the default) no automatic unmounts are done. Otherwise the file system backing the + infinity (the default) no automatic unmounts are done. Otherwise, the file system backing the automount point is detached after the last access and the idle timeout passed. See systemd.time7 for details on the time syntax supported. This option has no effect if only a regular mount is established, and automounting @@ -265,7 +265,7 @@ This option only has an effect in automount mode, and controls whether the automount unit shall be bound to the backing device's lifetime. If set, the - automount unit will be stopped automatically when the backing device vanishes. By default the automount unit + automount unit will be stopped automatically when the backing device vanishes. By default, the automount unit stays around, and subsequent accesses will block until backing device is replugged. This option has no effect in case of non-device mounts, such as network or virtual file system mounts. diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index a01e699080d..e3282793cda 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -351,7 +351,7 @@ Takes an image policy string as argument, as per systemd.image-policy7. The policy is enforced when operating on the disk image specified via , see - above. If not specified defaults to + above. If not specified, defaults to root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent:home=encrypted+unprotected+absent:srv=encrypted+unprotected+absent:esp=unprotected+absent:xbootldr=unprotected+absent:tmp=encrypted+unprotected+absent:var=encrypted+unprotected+absent, i.e. all recognized file systems in the image are used, but not the swap partition. @@ -363,7 +363,7 @@ Takes the path to an OCI runtime bundle to invoke, as specified in the OCI Runtime Specification. In - this case no .nspawn file is loaded, and the root directory and various settings are read + this case, no .nspawn file is loaded, and the root directory and various settings are read from the OCI runtime JSON data (but data passed on the command line takes precedence). @@ -375,7 +375,7 @@ Mount the container's root file system (and any other file systems contained in the container image) read-only. This has no effect on additional mounts made with , and similar options. This mode is implied if the container image file or directory is - marked read-only itself. It is also implied if is used. In this case the container + marked read-only itself. It is also implied if is used. In this case, the container image on disk is strictly read-only, while changes are permitted but kept non-persistently in memory only. For further details, see below. @@ -626,7 +626,7 @@ SIGTERM, in order to trigger an orderly shutdown of the container. Defaults to SIGRTMIN+3 if is used (on systemd-compatible init systems SIGRTMIN+3 triggers an orderly shutdown). If is not used and this - option is not specified the container's processes are terminated abruptly via SIGKILL. For + option is not specified, the container's processes are terminated abruptly via SIGKILL. For a list of valid signals, see signal7. @@ -1416,7 +1416,7 @@ After=sys-subsystem-net-devices-ens1.device It's recommended to use copy-… or replace-… if the container shall be able to make changes to the DNS configuration on its own, deviating from the - host's settings. Otherwise bind is preferable, as it means direct changes to + host's settings. Otherwise, bind is preferable, as it means direct changes to /etc/resolv.conf in the container are not allowed, as it is a read-only bind mount (but note that if the container has enough privileges, it might simply go ahead and unmount the bind mount anyway). Note that both if the file is bind mounted and if it is copied no further diff --git a/man/systemd-pcrlock.xml b/man/systemd-pcrlock.xml index b3a8320f8fb..89b989ea2da 100644 --- a/man/systemd-pcrlock.xml +++ b/man/systemd-pcrlock.xml @@ -453,7 +453,7 @@ Specifies the NV index to store the policy in. Honoured by - make-policy. If not specified the command will automatically pick a free NV + make-policy. If not specified, the command will automatically pick a free NV index. @@ -464,7 +464,7 @@ Takes a path to read *.pcrlock and *.pcrlock.d/*.pcrlock files from. May be used more than once to specify multiple - such directories. If not specified defaults to /etc/pcrlock.d/, + such directories. If not specified, defaults to /etc/pcrlock.d/, /run/pcrlock.d/, /var/lib/pcrlock.d/, /usr/local/pcrlock.d/, /usr/lib/pcrlock.d/. @@ -534,7 +534,7 @@ Takes a file system path as argument. If specified, configures where to write pcrlock - policy metadata to. If not specified defaults to + policy metadata to. If not specified, defaults to /var/lib/systemd/pcrlock.json. diff --git a/man/systemd-pcrphase.service.xml b/man/systemd-pcrphase.service.xml index 2dc9c8ada09..675683d8769 100644 --- a/man/systemd-pcrphase.service.xml +++ b/man/systemd-pcrphase.service.xml @@ -141,7 +141,7 @@ - Takes the PCR banks to extend the specified word into. If not specified the tool + Takes the PCR banks to extend the specified word into. If not specified, the tool automatically determines all enabled PCR banks and measures the word into all of them. @@ -173,7 +173,7 @@ If no TPM2 firmware, kernel subsystem, kernel driver or device support is found, exit - with exit status 0 (i.e. indicate success). If this is not specified any attempt to measure without a + with exit status 0 (i.e. indicate success). If this is not specified, any attempt to measure without a TPM2 device will cause the invocation to fail. diff --git a/man/systemd-repart.xml b/man/systemd-repart.xml index c6e2e306da8..fba81cd24b6 100644 --- a/man/systemd-repart.xml +++ b/man/systemd-repart.xml @@ -168,7 +168,7 @@ - Takes a boolean. If this switch is not specified is + Takes a boolean. If this switch is not specified, is the implied default. Controls whether systemd-repart executes the requested re-partition operations or whether it should only show what it would do. Unless is specified systemd-repart will not actually @@ -183,7 +183,7 @@ Takes one of refuse, allow, require, force or create. Controls how to operate on block devices that are entirely empty, i.e. carry no partition table/disk label yet. If - this switch is not specified the implied default is refuse. + this switch is not specified, the implied default is refuse. If refuse systemd-repart requires that the block device it shall operate on already carries a partition table and refuses operation if none is found. If @@ -202,7 +202,7 @@ - Takes a boolean. If this switch is not specified is + Takes a boolean. If this switch is not specified , is the implied default. Controls whether to issue the BLKDISCARD I/O control command on the space taken up by any added partitions or on the space in between them. Usually, it is a good idea to issue this request since it tells the underlying hardware that the covered blocks @@ -242,7 +242,7 @@ - Takes boolean. If this switch is not specified is + Takes boolean. If this switch is not specified, is the implied default. Controls whether to operate in "factory reset" mode, see above. If set to true this will remove all existing partitions marked with FactoryReset= set to yes early while executing the re-partitioning algorithm. Use with care, this is a great way to lose all @@ -299,7 +299,7 @@ Takes a UUID as argument or the special value random. If a UUID is specified the UUIDs to assign to partitions and the partition table itself are derived via - cryptographic hashing from it. If not specified it is attempted to read the machine ID from the host + cryptographic hashing from it. If not specified, it is attempted to read the machine ID from the host (or more precisely, the root directory configured via ) and use it as seed instead, falling back to a randomized seed otherwise. Use to force a randomized seed. Explicitly specifying the seed may be used to generated strictly reproducible @@ -337,8 +337,8 @@ Takes a file system path. Configures the encryption key to use when setting up LUKS2 volumes configured with the Encrypt=key-file setting in partition files. Should refer to a regular file containing the key, or an AF_UNIX stream socket in the - file system. In the latter case a connection is made to it and the key read from it. If this switch - is not specified the empty key (i.e. zero length key) is used. This behaviour is useful for setting + file system. In the latter case, a connection is made to it and the key read from it. If this switch + is not specified, the empty key (i.e. zero length key) is used. This behaviour is useful for setting up encrypted partitions during early first boot that receive their user-supplied password only in a later setup step. diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index 26921ff2baf..3bc3a01ab7e 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -224,7 +224,7 @@ and no global DNS server configured, one of the compiled-in fallback DNS servers is used. - Otherwise the unicast DNS query fails, as no suitable DNS servers can be determined. + Otherwise, the unicast DNS query fails, as no suitable DNS servers can be determined. diff --git a/man/systemd-run.xml b/man/systemd-run.xml index c8e0ca1a8ab..eeefe901dcf 100644 --- a/man/systemd-run.xml +++ b/man/systemd-run.xml @@ -675,7 +675,7 @@ There is a screen on: bash1 shell which is started by the service unit. The shell expands $SHELL to the path of the shell, and $$ to its process number, and then those strings are passed to the - echo built-in and printed to standard output (which in this case is connected to the + echo built-in and printed to standard output (which, in this case, is connected to the calling terminal). diff --git a/man/systemd-sbsign.xml b/man/systemd-sbsign.xml index ef30cb0d671..3c0bcf13eea 100644 --- a/man/systemd-sbsign.xml +++ b/man/systemd-sbsign.xml @@ -43,7 +43,7 @@ Signs the given PE binary for EFI Secure Boot. Takes a path to a PE binary as its argument. If the PE binary already has a certificate table, the new signature will be added to it. - Otherwise a new certificate table will be created. The signed PE binary will be written to the path + Otherwise, a new certificate table will be created. The signed PE binary will be written to the path specified with . diff --git a/man/systemd-sleep.conf.xml b/man/systemd-sleep.conf.xml index c02b44f3de6..dee442b01e8 100644 --- a/man/systemd-sleep.conf.xml +++ b/man/systemd-sleep.conf.xml @@ -139,7 +139,7 @@ AllowHybridSleep= AllowSuspendThenHibernate= - By default any power-saving mode is advertised if possible (i.e. + By default, any power-saving mode is advertised if possible (i.e. the kernel supports that mode, the necessary resources are available). Those switches can be used to disable specific modes. diff --git a/man/systemd-soft-reboot.service.xml b/man/systemd-soft-reboot.service.xml index 27f17a1f1e5..a72aecb05f1 100644 --- a/man/systemd-soft-reboot.service.xml +++ b/man/systemd-soft-reboot.service.xml @@ -58,7 +58,7 @@ The initrd initialization. - However this form of reboot comes with drawbacks as well: + However, this form of reboot comes with drawbacks as well: The OS update remains incomplete, as the kernel is not reset and continues diff --git a/man/systemd-ssh-proxy.xml b/man/systemd-ssh-proxy.xml index 8b81654bddb..786d16b3ee0 100644 --- a/man/systemd-ssh-proxy.xml +++ b/man/systemd-ssh-proxy.xml @@ -71,7 +71,7 @@ Host .host cloud-hypervisor VSOCK support and Using the Firecracker Virtio-vsock Device. - Moreover connecting to .host will connect to the local host via SSH, without + Moreover, connecting to .host will connect to the local host via SSH, without involving networking. This tool is supposed to be used together with diff --git a/man/systemd-storagetm.service.xml b/man/systemd-storagetm.service.xml index 25c5c4e4fc9..6172190157c 100644 --- a/man/systemd-storagetm.service.xml +++ b/man/systemd-storagetm.service.xml @@ -70,7 +70,7 @@ url="https://nvmexpress.org/wp-content/uploads/NVM-Express-Base-Specification-2.0c-2022.10.04-Ratified.pdf">NVM Express Base Specification 2.0c, section 4.5 "NVMe Qualified Names". Note that the NQN specified here will be suffixed with a dot and the block device name before it is exposed on the - NVMe target. If not specified defaults to + NVMe target. If not specified, defaults to nqn.2023-10.io.systemd:storagetm.ID, where ID is replaced by a 128bit ID derived from machine-id5. diff --git a/man/systemd-sysext.xml b/man/systemd-sysext.xml index ad3e0e8e043..43b5575a7d6 100644 --- a/man/systemd-sysext.xml +++ b/man/systemd-sysext.xml @@ -371,7 +371,7 @@ Takes an image policy string as argument, as per systemd.image-policy7. The - policy is enforced when operating on system extension disk images. If not specified defaults to + policy is enforced when operating on system extension disk images. If not specified, defaults to root=verity+signed+encrypted+unprotected+absent:usr=verity+signed+encrypted+unprotected+absent for system extensions, i.e. only the root and /usr/ file systems in the image are used. For configuration extensions defaults to diff --git a/man/systemd-system.conf.xml b/man/systemd-system.conf.xml index a6de3ab30b2..9bfd212a459 100644 --- a/man/systemd-system.conf.xml +++ b/man/systemd-system.conf.xml @@ -371,7 +371,7 @@ running and hence RuntimeWatchdogSec= is still honoured. In order to define a timeout on this first phase of system shutdown, configure JobTimeoutSec= and JobTimeoutAction= in the [Unit] section of the - shutdown.target unit. By default RuntimeWatchdogSec= defaults + shutdown.target unit. By default, RuntimeWatchdogSec= defaults to 0 (off), and RebootWatchdogSec= to 10min. KExecWatchdogSec= may be used to additionally enable the watchdog when kexec diff --git a/man/systemd-vmspawn.xml b/man/systemd-vmspawn.xml index 5934095d2c3..dfd3bbd7b4f 100644 --- a/man/systemd-vmspawn.xml +++ b/man/systemd-vmspawn.xml @@ -131,7 +131,7 @@ - If is not specified KVM support will be + If is not specified, KVM support will be detected automatically. If true, KVM is always used, and if false, KVM is never used. @@ -140,7 +140,7 @@ - If is not specified VSOCK networking support will be + If is not specified, VSOCK networking support will be detected automatically. If true, VSOCK networking is always used, and if false, VSOCK networking is never used. @@ -152,7 +152,7 @@ Sets the specific CID to use for the guest. Valid CIDs are in the range 3 to 4294967294 (0xFFFF_FFFE). - CIDs outside of this range are reserved. By default vmspawn will attempt to derive a CID for the guest derived from the machine name, + CIDs outside of this range are reserved. By default, vmspawn will attempt to derive a CID for the guest derived from the machine name, falling back to a random CID if this CID is taken. @@ -163,7 +163,7 @@ - If is not specified vmspawn will detect the presence of + If is not specified, vmspawn will detect the presence of swtpm8 and use it if available. If yes is specified swtpm8 is always used, and if no is set swtpm @@ -238,7 +238,7 @@ Takes an absolute path, or a relative path beginning with ./. Specifies a JSON firmware definition file, which allows selecting the - firmware to boot in the VM. If not specified a suitable firmware is automatically discovered. If the + firmware to boot in the VM. If not specified, a suitable firmware is automatically discovered. If the special string list is specified lists all discovered firmwares. @@ -259,9 +259,9 @@ Configure whether to search for firmware which supports Secure Boot. - If the option is not specified the first firmware which is detected will be used. - If the option is set to yes then the first firmware with Secure Boot support will be selected. - If no is specified then the first firmware without Secure Boot will be selected. + If the option is not specified, the first firmware which is detected will be used. + If the option is set to yes, then the first firmware with Secure Boot support will be selected. + If no is specified, then the first firmware without Secure Boot will be selected. @@ -402,7 +402,7 @@ - By default an SSH key is generated to allow systemd-vmspawn to open + By default, an SSH key is generated to allow systemd-vmspawn to open a D-Bus connection to the VM's systemd bus. Setting this to "no" will disable SSH key generation. The generated keys are ephemeral. That is they are valid only for the current invocation of systemd-vmspawn, @@ -419,7 +419,7 @@ ssh-keygen1 for more information. - By default ed25519 keys are generated, however rsa keys + By default, ed25519 keys are generated, however rsa keys may also be useful if the VM has a particularly old version of sshd8. @@ -566,7 +566,7 @@ $ ssh root@vsock/$my_vsock_cid -i /run/user/$UID/systemd/vmspawn/machine-*-syste If an error occurred the value errno is propagated to the return code. If EXIT_STATUS is supplied by the running image that is returned. - Otherwise EXIT_SUCCESS is returned. + Otherwise, EXIT_SUCCESS is returned. diff --git a/man/systemd-vpick.xml b/man/systemd-vpick.xml index eb067148df3..010701637e6 100644 --- a/man/systemd-vpick.xml +++ b/man/systemd-vpick.xml @@ -81,7 +81,7 @@ Explicitly configures the architecture to select. If specified, a filename with the - specified architecture identifier will be looked for. If not specified only filenames with a locally + specified architecture identifier will be looked for. If not specified, only filenames with a locally supported architecture are considered, or those without any architecture identifier. @@ -117,7 +117,7 @@ - Configures what precisely to write to standard output. If not specified prints the + Configures what precisely to write to standard output. If not specified, prints the full, resolved path of the newest matching file in the .v/ directory. This switch can be set to one of the following: diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index d7a792f1a4c..b1fcfecd74f 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -458,14 +458,14 @@ is already marked read-only), while BindReadOnlyPaths= creates read-only bind mounts. These settings may be used more than once, each usage appends to the unit's list of bind mounts. If the empty string is assigned to either of these two options the entire list of bind mounts defined prior to this is reset. Note - that in this case both read-only and regular bind mounts are reset, regardless which of the two settings is + that, in this case, both read-only and regular bind mounts are reset, regardless which of the two settings is used. Using this option implies that a mount namespace is allocated for the unit, i.e. it implies the effect of PrivateMounts= (see below). This option is particularly useful when RootDirectory=/RootImage= - is used. In this case the source path refers to a path on the host file system, while the destination path + is used. In this case, the source path refers to a path on the host file system, while the destination path refers to a path below the root directory of the unit. Note that the destination directory must exist or systemd must be able to create it. Thus, it @@ -697,7 +697,7 @@ leave files around after unit termination. Furthermore NoNewPrivileges= and RestrictSUIDSGID= are implicitly enabled (and cannot be disabled), to ensure that processes invoked cannot take benefit or create SUID/SGID - files or directories. Moreover ProtectSystem=strict and + files or directories. Moreover, ProtectSystem=strict and ProtectHome=read-only are implied, thus prohibiting the service to write to arbitrary file system locations. In order to allow the service to write to certain directories, they have to be allow-listed using ReadWritePaths=, but care must be taken so that @@ -835,7 +835,7 @@ CapabilityBoundingSet=~CAP_B CAP_C capabilities to the ambient capability set adds them to the process's inherited capability set. Ambient capability sets are useful if you want to execute a process as a non-privileged user but - still want to give it some capabilities. Note that in this case option keep-caps + still want to give it some capabilities. Note that, in this case, option keep-caps is automatically added to SecureBits= to retain the capabilities over the user change. AmbientCapabilities= does not affect commands prefixed with +. @@ -1219,7 +1219,7 @@ CapabilityBoundingSet=~CAP_B CAP_C executed processes. Takes an integer between -1000 (to disable OOM killing of processes of this unit) and 1000 (to make killing of processes of this unit under memory pressure very likely). See The /proc Filesystem for - details. If not specified defaults to the OOM score adjustment level of the service manager itself, + details. If not specified, defaults to the OOM score adjustment level of the service manager itself, which is normally at 0. Use the OOMPolicy= setting of service units to configure how the service @@ -1805,7 +1805,7 @@ BindReadOnlyPaths=/var/lib/systemd ReadOnlyPaths= and related calls, see above. If set to true (as opposed to disconnected), this has the side effect of adding Requires= and After= dependencies on all mount units necessary - to access /tmp/ and /var/tmp/ on the host. Moreover an + to access /tmp/ and /var/tmp/ on the host. Moreover, an implicitly After= ordering on systemd-tmpfiles-setup.service8 is added. @@ -3140,7 +3140,7 @@ SystemCallErrorNumber=EPERM If the standard output (or error output, see below) of a unit is connected to the journal or the kernel log buffer, the unit will implicitly gain a dependency of type After= on systemd-journald.socket (also see the "Implicit Dependencies" section - above). Also note that in this case stdout (or stderr, see below) will be an + above). Also note that, in this case, stdout (or stderr, see below) will be an AF_UNIX stream socket, and not a pipe or FIFO that can be reopened. This means when executing shell scripts the construct echo "hello" > /dev/stderr for writing text to stderr will not work. To mitigate this use the construct echo "hello" @@ -3225,7 +3225,7 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX , , (highest log level, also lowest priority messages). See syslog3 for - details. By default no filtering is applied (i.e. the default maximum log level is ). Use + details. By default, no filtering is applied (i.e. the default maximum log level is ). Use this option to configure the logging system to drop log messages of a specific service above the specified level. For example, set LogLevelMax= in order to turn off debug logging of a particularly chatty unit. Note that the configured level is applied to any log messages written by any @@ -3571,7 +3571,7 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX url="https://www.dmtf.org/standards/smbios">DMI/SMBIOS OEM string table entries (field type 11) with a prefix of io.systemd.credential: or io.systemd.credential.binary:. In both cases a key/value pair separated by - = is expected, in the latter case the right-hand side is Base64 decoded when + = is expected. In the latter case, the right-hand side is Base64 decoded when parsed (thus permitting binary data to be passed in). Example qemu switch: -smbios type=11,value=io.systemd.credential:xx=yy, or -smbios @@ -3673,7 +3673,7 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX LoadCredential=, LoadCredentialEncrypted= and ImportCredential= take priority over credentials found by SetCredential=. As such, SetCredential= will act as default if - no credentials are found by any of the former. In this case not being able to retrieve the credential + no credentials are found by any of the former. In this case, not being able to retrieve the credential from the path specified in LoadCredential= or LoadCredentialEncrypted= is not considered fatal. diff --git a/man/systemd.generator.xml b/man/systemd.generator.xml index ce09a6648ff..589c057dd94 100644 --- a/man/systemd.generator.xml +++ b/man/systemd.generator.xml @@ -99,7 +99,7 @@ Output directories Generators are invoked with three arguments: paths to directories where generators can place their - generated unit files or symlinks. By default those paths are runtime directories that are included in the + generated unit files or symlinks. By default, those paths are runtime directories that are included in the search path of systemd, but a generator may be called with different paths for debugging purposes. If only one argument is provided, the generator should use the same directory as the three output paths. diff --git a/man/systemd.link.xml b/man/systemd.link.xml index 28e175bde43..ae478b555d2 100644 --- a/man/systemd.link.xml +++ b/man/systemd.link.xml @@ -889,7 +889,7 @@ - By default this is unset, i.e. all possible modes will be advertised. + By default, this is unset, i.e. all possible modes will be advertised. This option may be specified more than once, in which case all specified speeds and modes are advertised. If the empty string is assigned to this option, the list is reset, and all prior assignments have no effect. diff --git a/man/systemd.mount.xml b/man/systemd.mount.xml index 73d5e28e721..3043e904995 100644 --- a/man/systemd.mount.xml +++ b/man/systemd.mount.xml @@ -471,7 +471,7 @@ With , this mount will be only wanted, not required, by - local-fs.target or remote-fs.target. Moreover the mount unit is not + local-fs.target or remote-fs.target. Moreover, the mount unit is not ordered before these target units. This means that the boot will continue without waiting for the mount unit and regardless whether the mount point can be mounted successfully. diff --git a/man/systemd.netdev.xml b/man/systemd.netdev.xml index 70d34189028..d072501a458 100644 --- a/man/systemd.netdev.xml +++ b/man/systemd.netdev.xml @@ -834,7 +834,7 @@ to provide protocol typing, OAM, and versioning capabilities. For details about the VXLAN GPE Header, see the Generic Protocol Extension for VXLAN document. If destination port is not specified and - Generic Protocol Extension is set then default port of 4790 is used. Defaults to false. + Generic Protocol Extension is set, the default port of 4790 is used. Defaults to false. @@ -842,7 +842,7 @@ DestinationPort= - Configures the default destination UDP port. If the destination port is not specified then + Configures the default destination UDP port. If the destination port is not specified, the Linux kernel default will be used. Set to 4789 to get the IANA assigned value. diff --git a/man/systemd.network.xml b/man/systemd.network.xml index c71634e70af..6ed4dde4df4 100644 --- a/man/systemd.network.xml +++ b/man/systemd.network.xml @@ -811,7 +811,7 @@ DuplicateAddressDetection=none resolving domain names that do not match any link's configured Domains= setting. If false, this link's configured DNS servers are never used for such domains, and are exclusively used for resolving names that match at least one of the domains configured on - this link. If not specified defaults to an automatic mode: queries not matching any link's + this link. If not specified, defaults to an automatic mode: queries not matching any link's configured domains will be routed to this link if it has no routing-only domains configured. @@ -994,7 +994,7 @@ DuplicateAddressDetection=none route to the source on that interface, the machine will drop the packet. Takes one of no, strict, or loose. When no, no source validation will be done. When strict, each incoming packet is tested against the FIB and - if the incoming interface is not the best reverse path, the packet check will fail. By default failed packets are discarded. + if the incoming interface is not the best reverse path, the packet check will fail. By default, failed packets are discarded. When loose, each incoming packet's source address is tested against the FIB. The packet is dropped only if the source address is not reachable via any interface on that router. See RFC 3704. @@ -1080,7 +1080,7 @@ DuplicateAddressDetection=none Takes a boolean. Configures proxy NDP for IPv6. Proxy NDP (Neighbor Discovery Protocol) is a technique for IPv6 to allow routing of addresses to a different destination when peers - expect them to be present on a certain physical link. In this case a router answers Neighbour + expect them to be present on a certain physical link. In this case, a router answers Neighbour Advertisement messages intended for another machine by offering its own MAC address as destination. Unlike proxy ARP for IPv4, it is not enabled globally, but will only send Neighbour Advertisement messages for addresses in the IPv6 neighbor proxy table, which can @@ -2720,7 +2720,7 @@ NFTSet=prefix:netdev:filter:eth_ipv4_prefix added to the routing table with a metric of 1024, and a scope of , or , depending on the route's destination and gateway. If the destination is on the local host, e.g., 127.x.x.x, or the same as the link's - own address, the scope will be set to . Otherwise if the gateway is null + own address, the scope will be set to . Otherwise, if the gateway is null (a direct route), a scope will be used. For anything else, scope defaults to . @@ -4828,7 +4828,7 @@ ServerAddress=192.168.0.1/24 triggered automatically in case of a bus-off condition after the specified delay time. Subsecond delays can be specified using decimals (e.g. 0.1s) or a ms or us postfix. Using infinity or 0 will turn the - automatic restart off. By default automatic restart is disabled. + automatic restart off. By default, automatic restart is disabled. diff --git a/man/systemd.resource-control.xml b/man/systemd.resource-control.xml index 84d1bfa0d33..a2f1bc02baa 100644 --- a/man/systemd.resource-control.xml +++ b/man/systemd.resource-control.xml @@ -797,7 +797,7 @@ CPUWeight=20 DisableControllers=cpu / \ The access lists configured with this option are applied to all sockets created by processes of this unit (or in the case of socket units, associated with it). The lists are implicitly combined with any lists configured for any of the parent slice units this unit might be a member - of. By default both access lists are empty. Both ingress and egress traffic is filtered by these + of. By default, both access lists are empty. Both ingress and egress traffic is filtered by these settings. In case of ingress traffic the source IP address is checked against these access lists, in case of egress traffic the destination IP address is checked. The following rules are applied in turn: @@ -998,7 +998,7 @@ SocketBindDeny=any Takes a list of space-separated network interface names. This option restricts the network - interfaces that processes of this unit can use. By default processes can only use the network interfaces + interfaces that processes of this unit can use. By default, processes can only use the network interfaces listed (allow-list). If the first character of the rule is ~, the effect is inverted: the processes can only use network interfaces not listed (deny-list). @@ -1150,7 +1150,7 @@ NFTSet=cgroup:inet:filter:my_service user:inet:filter:serviceuser of this unit (or in the case of socket units, associated with it). The filters are loaded in addition to filters any of the parent slice units this unit might be a member of as well as any IPAddressAllow= and IPAddressDeny= filters in any of these units. - By default there are no filters specified. + By default, there are no filters specified. If these settings are used multiple times in the same unit all the specified programs are attached. If an empty string is assigned to these settings the program list is reset and all previous specified programs ignored. @@ -1647,7 +1647,7 @@ DeviceAllow=/dev/loop-control Sets the memory pressure threshold time for memory pressure monitor as configured via MemoryPressureWatch=. Specifies the maximum allocation latency before a memory - pressure event is signalled to the service, per 2s window. If not specified defaults to the + pressure event is signalled to the service, per 2s window. If not specified, defaults to the DefaultMemoryPressureThresholdSec= setting in systemd-system.conf5 (which in turn defaults to 200ms). The specified value expects a time unit such as diff --git a/man/systemd.special.xml b/man/systemd.special.xml index 17f3c84bef2..6093761b8f2 100644 --- a/man/systemd.special.xml +++ b/man/systemd.special.xml @@ -724,7 +724,7 @@ A special target unit that sets up all slice units (see systemd.slice5 - for details) that shall always be active after boot. By default the generic + for details) that shall always be active after boot. By default, the generic system.slice slice unit as well as the root slice unit -.slice are pulled in and ordered before this unit (see below). diff --git a/man/systemd.time.xml b/man/systemd.time.xml index 8348d6bd63f..820e5e499ec 100644 --- a/man/systemd.time.xml +++ b/man/systemd.time.xml @@ -101,7 +101,7 @@ In some cases timestamps are shown in the UTC timezone instead of the local timezone, which is indicated via the UTC timezone specifier in the output. - In some cases timestamps are shown with microsecond granularity. In this case the sub-second remainder is + In some cases timestamps are shown with microsecond granularity. In this case, the sub-second remainder is separated by a full stop from the seconds component. diff --git a/man/systemd.timer.xml b/man/systemd.timer.xml index 2ea56d687fa..f2035a541f4 100644 --- a/man/systemd.timer.xml +++ b/man/systemd.timer.xml @@ -198,7 +198,7 @@ it is subject to the AccuracySec= setting below. May be specified more than once, in which case the timer unit will trigger whenever any of the - specified expressions elapse. Moreover calendar timers and monotonic timers (see above) may be + specified expressions elapse. Moreover, calendar timers and monotonic timers (see above) may be combined within the same timer unit. If the empty string is assigned to any of these options, the list of timers is reset (both diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 2b1f953b4fc..986505e29f7 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -208,7 +208,7 @@ section headers. For instantiated units, this logic will first look for the instance .d/ subdirectory (e.g. foo@bar.service.d/) and read its .conf files, followed by the template .d/ subdirectory (e.g. - foo@.service.d/) and the .conf files there. Moreover for unit + foo@.service.d/) and the .conf files there. Moreover, for unit names containing dashes (-), the set of directories generated by repeatedly truncating the unit name after all dashes is searched too. Specifically, for a unit name foo-bar-baz.service not only the regular drop-in directory @@ -582,7 +582,7 @@ signals, resource consumption and other statistics are lost, except for what is stored in the log subsystem. Use systemctl daemon-reload or an equivalent command to reload unit configuration while - the unit is already loaded. In this case all configuration settings are flushed out and replaced with the new + the unit is already loaded. In this case, all configuration settings are flushed out and replaced with the new configuration (which however might not be in effect immediately), however all runtime state is saved/restored. @@ -1066,7 +1066,7 @@ is not unloaded if it is in the failed state. In mode, failed units are not unloaded until the user invoked systemctl reset-failed on them to reset the failed state, or an equivalent command. This behaviour is altered if this option is set to - : in this case the unit is unloaded even if the unit is in a + : in this case, the unit is unloaded even if the unit is in a failed state, and thus an explicitly resetting of the failed state is not necessary. Note that if this mode is used unit results (such as exit codes, exit signals, consumed resources, …) are flushed out immediately after the unit completed, except for what is stored in the logging @@ -1122,7 +1122,7 @@ Controls the exit status to propagate back to an invoking container manager (in case of a system service) or service manager (in case of a user manager) when the FailureAction=/SuccessAction= are set to or - and the action is triggered. By default the exit status of the main process of the + and the action is triggered. By default, the exit status of the main process of the triggering unit (if this applies) is propagated. Takes a value in the range 0…255 or the empty string to request default behaviour. @@ -1833,7 +1833,7 @@ for use on the system or whether the legacy v1 cgroup or the modern v2 cgroup hierarchy is used. - Multiple controllers may be passed with a space separating them; in this case the condition + Multiple controllers may be passed with a space separating them; in this case, the condition will only pass if all listed controllers are available for use. Controllers unknown to systemd are ignored. Valid controllers are cpu, io, memory, and pids. Even if available in the kernel, a @@ -2173,7 +2173,7 @@ implicitly along with their reverses and cannot be specified directly. Note: Triggers= is created implicitly between a socket, - path unit, or an automount unit, and the unit they activate. By default a unit + path unit, or an automount unit, and the unit they activate. By default, a unit with the same name is triggered, but this can be overridden using Sockets=, Service=, and Unit= settings. See diff --git a/man/systemd.v.xml b/man/systemd.v.xml index a340d1e4b79..cee351448c1 100644 --- a/man/systemd.v.xml +++ b/man/systemd.v.xml @@ -143,7 +143,7 @@ /var/lib/machines/mymachine.raw.v/mymachine_7.5.14_x86-64.raw. Explanation: even though mymachine_7.7.0_x86-64+0-5.raw has the newest version, it is not preferred because its tries left counter is zero. And even though mymachine_7.6.0_arm64.raw - has the second newest version it is also not considered, in this case because we operate on an x86_64 + has the second newest version it is also not considered in this case, because we operate on an x86_64 system and the image is intended for arm64 CPUs. Finally, the mymachine_7.5.13.raw image is not considered because it is older than mymachine_7.5.14_x86-64.raw. diff --git a/man/sysupdate.d.xml b/man/sysupdate.d.xml index 5c9a7428baa..f9ad7cb64ae 100644 --- a/man/sysupdate.d.xml +++ b/man/sysupdate.d.xml @@ -617,7 +617,7 @@ optional. If the source type is regular-file or directory, the - pattern may contain slash characters. In this case it will match the file or directory in + pattern may contain slash characters. In this case, it will match the file or directory in corresponding subdirectory. For example MatchPattern=foo_@v/bar.efi will match bar.efi in directory foo_1. @@ -713,7 +713,7 @@ naming newly installed versions. If the target type is regular-file or directory, the - pattern may contain slash characters. In this case it will match the file or directory in + pattern may contain slash characters. In this case, it will match the file or directory in corresponding subdirectory. For example MatchPattern=foo_@v/bar.efi will match bar.efi in directory foo_1. Directories in the path will be created when file is installed. Empty directories will be removed when file is removed. diff --git a/man/tmpfiles.d.xml b/man/tmpfiles.d.xml index 536f9539d78..c29c514b5e1 100644 --- a/man/tmpfiles.d.xml +++ b/man/tmpfiles.d.xml @@ -575,7 +575,7 @@ w- /proc/sys/vm/swappiness - - - - 10 removed unless applied to a directory. This functionality is particularly useful in conjunction with Z. - By default the access mode of listed inodes is set to the specified mode regardless of whether it is + By default, the access mode of listed inodes is set to the specified mode regardless of whether it is created anew, or already existed. Optionally, if prefixed with :, the configured access mode is only applied when creating new inodes, and if the inode the line refers to already exists, its access mode is left in place unmodified. @@ -601,7 +601,7 @@ w- /proc/sys/vm/swappiness - - - - 10 Resolvability of User and Group Names for more information on requirements on system user/group definitions. - By default the ownership of listed inodes is set to the specified user/group regardless of whether it is + By default, the ownership of listed inodes is set to the specified user/group regardless of whether it is created anew, or already existed. Optionally, if prefixed with :, the configured user/group information is only applied when creating new inodes, and if the inode the line refers to already exists, its user/group is left in place unmodified. diff --git a/man/userdbctl.xml b/man/userdbctl.xml index 43ba804b0c0..e1bd4627201 100644 --- a/man/userdbctl.xml +++ b/man/userdbctl.xml @@ -91,7 +91,7 @@ Controls which services to query for users/groups. Takes a list of one or more service names, separated by :. See below for a list of well-known service - names. If not specified all available services are queried at once. + names. If not specified, all available services are queried at once. @@ -136,7 +136,7 @@ Controls whether to synthesize records for the root and nobody users/groups if they - are not defined otherwise. By default (or yes) such records are implicitly + are not defined otherwise. By default (or yes), such records are implicitly synthesized if otherwise missing since they have special significance to the OS. When no this synthesizing is turned off. @@ -289,7 +289,7 @@ groups-of-user USER… List groups that the specified users are members of. If no users are specified list - all user/group memberships defined (in this case groups-of-user and + all user/group memberships defined (in this case, groups-of-user and users-in-group are equivalent). Use to tweak output mode. diff --git a/man/varlinkctl.xml b/man/varlinkctl.xml index ce49b29f9d4..eb23e5099d1 100644 --- a/man/varlinkctl.xml +++ b/man/varlinkctl.xml @@ -80,11 +80,11 @@ A Varlink service reference starting with the unix: string, followed by an absolute AF_UNIX socket path, or by @ and an arbitrary - string (the latter for referencing sockets in the abstract namespace). In this case a stream socket + string (the latter for referencing sockets in the abstract namespace). In this case, a stream socket connection is made to the specified socket. A Varlink service reference starting with the exec: string, followed - by an absolute path of a binary to execute. In this case the specified process is forked off locally, + by an absolute path of a binary to execute. In this case, the specified process is forked off locally, with a connected stream socket passed in. A Varlink service reference starting with the ssh-unix: string, followed @@ -94,11 +94,11 @@ A Varlink service reference starting with the ssh-exec: string, followed by an SSH host specification, followed by :, followed by a command line. In - this case the command is invoked and the Varlink protocol is spoken on the standard input and output of + this case, the command is invoked and the Varlink protocol is spoken on the standard input and output of the invoked command. - For convenience these two simpler (redundant) service address syntaxes are also supported: + For convenience, these two simpler (redundant) service address syntaxes are also supported: A file system path to an AF_UNIX socket, either absolute @@ -174,7 +174,7 @@ Reads a Varlink interface definition file, parses and validates it, then outputs it with syntax highlighting. This checks for syntax and internal consistency of the interface. Expects a - file name to read the interface definition from. If omitted reads the interface definition from + file name to read the interface definition from. If omitted, reads the interface definition from STDIN. @@ -300,7 +300,7 @@ - Expects a timeout in seconds as parameter. By default a timeout of 45s is enforced. To turn + Expects a timeout in seconds as parameter. By default, a timeout of 45s is enforced. To turn off the timeout specify infinity or an empty string.