diff --git a/man/pam_systemd_home.xml b/man/pam_systemd_home.xml index 5bd48de4a6..ae3a24faf0 100644 --- a/man/pam_systemd_home.xml +++ b/man/pam_systemd_home.xml @@ -66,7 +66,7 @@ mechanism and console logins that do not, the home directory is not locked during suspend, due to the logic explained above. That said, it is possible to set this field for TTY logins too, ignoring the fact that TTY logins actually don't support the re-authentication mechanism. In that case the TTY - sessions will appear hung until the user logs in on another virtual terminal (regardless if via + sessions will appear hung until the user logs in on another virtual terminal (regardless of whether via another TTY session or graphically) which will resume the home directory and unblock the original TTY session. (Do note that lack of screen locking on TTY sessions means even though the TTY session appears hung, keypresses can still be queued into it, and the existing screen contents be read diff --git a/man/resolvectl.xml b/man/resolvectl.xml index 44c0e6622f..4e3b35a330 100644 --- a/man/resolvectl.xml +++ b/man/resolvectl.xml @@ -399,7 +399,7 @@ Takes a boolean parameter; used in conjunction with query. If true (the default), lookups use the local DNS resource record cache. If false, lookups are routed to the - network instead, regardless if already available in the local cache. + network instead, regardless of whether already available in the local cache. diff --git a/man/sd_bus_track_add_name.xml b/man/sd_bus_track_add_name.xml index a7be6a24b8..98ec3b30af 100644 --- a/man/sd_bus_track_add_name.xml +++ b/man/sd_bus_track_add_name.xml @@ -126,7 +126,7 @@ sd_bus_track_count() returns the number of names currently being tracked by the specified bus peer tracking object. Note that this function always returns the actual number of names tracked, and hence if sd_bus_track_add_name() has been invoked multiple times for the same name it is only - counted as one, regardless if recursive mode is used or not. + counted as one, regardless of whether recursive mode is used or not. sd_bus_track_count_name() returns the current per-name counter for the specified name. If non-recursive mode is used this returns either 1 or 0, depending on whether the specified name has been diff --git a/man/sd_event_add_child.xml b/man/sd_event_add_child.xml index fa2361d221..36b83e6f07 100644 --- a/man/sd_event_add_child.xml +++ b/man/sd_event_add_child.xml @@ -202,7 +202,7 @@ sd_event_source_get_child_pidfd() retrieves the file descriptor referencing the watched process ("pidfd") if this functionality is available. On kernels that support the concept the - event loop will make use of pidfds to watch child processes, regardless if the individual event sources + event loop will make use of pidfds to watch child processes, regardless of whether the individual event sources are allocated via sd_event_add_child() or sd_event_add_child_pidfd(). If the latter call was used to allocate the event source, this function returns the file descriptor used for allocation. On kernels that do not support the diff --git a/man/systemd-mount.xml b/man/systemd-mount.xml index 05357b06b1..7bf366eabd 100644 --- a/man/systemd-mount.xml +++ b/man/systemd-mount.xml @@ -310,7 +310,7 @@ all mount units that mount and failed are kept in memory until the user explicitly resets their failure state with systemctl reset-failed or an equivalent command. On the other hand, units that stopped successfully are unloaded immediately. If this option is turned on the "garbage collection" of units is more - aggressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for + aggressive, and unloads units regardless of whether they exited successfully or failed. This option is a shortcut for --property=CollectMode=inactive-or-failed, see the explanation for CollectMode= in systemd.unit5 for further diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 7bdb55d5d5..5838424b82 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -400,7 +400,7 @@ Note that if one of the volatile modes is chosen, its effect is limited to the root file system (or /var/ in case of ), and any other mounts placed in the - hierarchy are unaffected — regardless if they are established automatically (e.g. the EFI system + hierarchy are unaffected — regardless of whether they are established automatically (e.g. the EFI system partition that might be mounted to /efi/ or /boot/) or explicitly (e.g. through an additional command line option such as , see below). This means, even if is used changes to diff --git a/man/systemd-run.xml b/man/systemd-run.xml index df31e2b168..e5b6f75f1e 100644 --- a/man/systemd-run.xml +++ b/man/systemd-run.xml @@ -475,7 +475,7 @@ all units that ran and failed are kept in memory until the user explicitly resets their failure state with systemctl reset-failed or an equivalent command. On the other hand, units that ran successfully are unloaded immediately. If this option is turned on the "garbage collection" of units is more - aggressive, and unloads units regardless if they exited successfully or failed. This option is a shortcut for + aggressive, and unloads units regardless of whether they exited successfully or failed. This option is a shortcut for --property=CollectMode=inactive-or-failed, see the explanation for CollectMode= in systemd.unit5 for further diff --git a/man/systemd-stub.xml b/man/systemd-stub.xml index 902b4013a0..921abb7e23 100644 --- a/man/systemd-stub.xml +++ b/man/systemd-stub.xml @@ -526,7 +526,7 @@ Similar to LoaderDevicePartUUID and StubImageIdentifier, but indicates the location of the unified kernel image EFI - binary rather than the location of the boot loader binary, regardless if booted via a boot loader + binary rather than the location of the boot loader binary, regardless of whether booted via a boot loader or not. diff --git a/man/systemd-sysext.xml b/man/systemd-sysext.xml index bf47e7ca55..ad3e0e8e04 100644 --- a/man/systemd-sysext.xml +++ b/man/systemd-sysext.xml @@ -204,8 +204,8 @@ component over the immutable OS image without doing a full OS rebuild or modifying the nominally immutable image. (e.g. "install" a locally built package with DESTDIR=/var/lib/extensions/mytest make install && systemd-sysext refresh, making it available in - /usr/ as if it was installed in the OS image itself.) This case works regardless if - the underlying host /usr/ is managed as immutable disk image or is a traditional + /usr/ as if it was installed in the OS image itself.) This case works regardless of + whether the underlying host /usr/ is managed as immutable disk image or is a traditional package manager controlled (i.e. writable) tree. With systemd-confext one can perform runtime reconfiguration of OS services. diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index f4917f59c1..8d1737c7bc 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -2035,7 +2035,7 @@ BindReadOnlyPaths=/var/lib/systemd process capability isolation. If this mode is enabled, all unit processes are run without privileges in the host user - namespace (regardless if the unit's own user/group is root or not). Specifically + namespace (regardless of whether the unit's own user/group is root or not). Specifically this means that the process will have zero process capabilities on the host's user namespace, but full capabilities within the service's user namespace. Settings such as CapabilityBoundingSet= will affect only the latter, and there's no way to acquire @@ -3327,7 +3327,7 @@ StandardInputData=V2XigLJyZSBubyBzdHJhbmdlcnMgdG8gbG92ZQpZb3Uga25vdyB0aGUgcnVsZX user-defined string identifying the namespace. If not used the processes of the service are run in the default journal namespace, i.e. their log stream is collected and processed by systemd-journald.service. If this option is used any log data generated by - processes of this unit (regardless if via the syslog(), journal native logging + processes of this unit (regardless of whether via the syslog(), journal native logging or stdout/stderr logging) is collected and processed by an instance of the systemd-journald@.service template unit, which manages the specified namespace. The log data is stored in a data store independent from the default log namespace's data diff --git a/man/systemd.image-policy.xml b/man/systemd.image-policy.xml index ed4af463b6..9ae959cf61 100644 --- a/man/systemd.image-policy.xml +++ b/man/systemd.image-policy.xml @@ -149,7 +149,7 @@ included in the image, regardless whether the configured image policy would allow access to it or not. Similar, systemd-nspawn1 is not - going to make use of any discovered swap device, regardless if the policy would allow that or not. + going to make use of any discovered swap device, regardless of whether the policy would allow that or not. Use the image-policy command of the systemd-analyze1 tool diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 8c90198e23..f17e3efcce 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -620,7 +620,7 @@ sd_notify3). - Note that the start timeout is also applied to service reloads, regardless if implemented + Note that the start timeout is also applied to service reloads, regardless of whether implemented through ExecReload= or via the reload logic enabled via Type=notify-reload. If the reload does not complete within the configured time, the reload will be considered failed and the service will continue running with the old configuration. This will not affect the running service, diff --git a/man/systemd.special.xml b/man/systemd.special.xml index b344775137..17f3c84bef 100644 --- a/man/systemd.special.xml +++ b/man/systemd.special.xml @@ -1187,7 +1187,7 @@ milestone indicating if and when SSH access into the system is available. It should only become active when an SSH port is bound for remote clients (i.e. if SSH is used as a local privilege escalation mechanism, it should not involve this target unit), regardless of - the protocol choices, i.e. regardless if IPv4, IPv6 or AF_VSOCK is + the protocol choices, i.e. regardless of whether IPv4, IPv6 or AF_VSOCK is used. diff --git a/man/tmpfiles.d.xml b/man/tmpfiles.d.xml index 8fb7aca7c6..a66774555b 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 if 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 if 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 a8bbfe7c7b..924de89d4b 100644 --- a/man/userdbctl.xml +++ b/man/userdbctl.xml @@ -425,7 +425,7 @@ AuthorizedKeysCommandUser root Sometimes it's useful to allow chain invocation of another program to list SSH authorized keys. By using the such a tool may be chain executed by userdbctl - ssh-authorized-keys once a lookup completes (regardless if an SSH key was found or + ssh-authorized-keys once a lookup completes (regardless of whether an SSH key was found or not). Example: … diff --git a/man/varlinkctl.xml b/man/varlinkctl.xml index dd3741aa0b..ce49b29f9d 100644 --- a/man/varlinkctl.xml +++ b/man/varlinkctl.xml @@ -208,8 +208,8 @@ If this mode is enabled output is automatically switched to JSON-SEQ mode, so that individual reply objects can be easily discerned. - This switch has no effect on the method call timeout applied by default: regardless if - is specified or not, the default timeout will be 45s. Use + This switch has no effect on the method call timeout applied by default: regardless of + whether is specified or not, the default timeout will be 45s. Use (see below) to change or disable the timeout. When invoking a method call that continuously returns updates it is typically desirable to disable the timeout with . On the other hand, when invoking a