From be0d27ee0c2a2cce39490b8cfc0e7d995fbd7644 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Tue, 27 Jul 2021 09:37:29 +0200 Subject: [PATCH] man: fix assorted issues reported by the manpage-l10n project Fixes #20297. --- man/bootctl.xml | 4 ++-- man/coredump.conf.xml | 19 ++++++---------- man/coredumpctl.xml | 2 +- man/os-release.xml | 2 +- man/repart.d.xml | 14 ++++++------ man/systemd-cryptenroll.xml | 2 +- man/systemd-firstboot.xml | 2 +- man/systemd-machine-id-setup.xml | 2 +- man/systemd-nspawn.xml | 18 +++++++-------- man/systemd-resolved.service.xml | 2 +- man/systemd-sysext.xml | 18 ++++++++------- man/systemd-system.conf.xml | 2 +- man/systemd-userdbd.service.xml | 2 +- man/systemd.exec.xml | 15 +++++++------ man/systemd.link.xml | 10 ++++----- man/systemd.netdev.xml | 38 ++++++++++++++++---------------- man/systemd.network.xml | 32 +++++++++++++-------------- man/systemd.nspawn.xml | 2 +- man/systemd.preset.xml | 2 +- man/systemd.service.xml | 2 +- man/systemd.unit.xml | 2 +- man/userdbctl.xml | 6 ++--- 22 files changed, 98 insertions(+), 100 deletions(-) diff --git a/man/bootctl.xml b/man/bootctl.xml index 81033158f64..d05c3f34d07 100644 --- a/man/bootctl.xml +++ b/man/bootctl.xml @@ -240,8 +240,8 @@ Control creation and deletion of the top-level machine ID directory on the file - system containing boot loader entries (i.e. beneath the file system returned by - above) during and + system containing boot loader entries (i.e. beneath the file system returned by the + option, see above) during and , respectively. auto is equivalent to yes if /etc/machine-id resides on a filesystem other than tmpfs and no otherwise (in the latter case the machine ID is likely transient and diff --git a/man/coredump.conf.xml b/man/coredump.conf.xml index 28e6017c7db..1751191ec0c 100644 --- a/man/coredump.conf.xml +++ b/man/coredump.conf.xml @@ -83,12 +83,9 @@ ProcessSizeMax= - The maximum size in bytes of a core - which will be processed. Core dumps exceeding this size - may be stored, but the backtrace will not be generated. - Like other sizes in this same config file, the usual - suffixes to the base of 1024 are allowed (B, K, M, - G, T, P, and E.) + The maximum size in bytes of a core which will be processed. Core dumps exceeding + this size may be stored, but the backtrace will not be generated. Like other sizes in this same + config file, the usual suffixes to the base of 1024 are allowed (B, K, M, G, T, P, and E). Setting Storage=none and ProcessSizeMax=0 disables all coredump handling except for a log entry. @@ -99,9 +96,8 @@ ExternalSizeMax= JournalSizeMax= - The maximum (compressed or uncompressed) size in bytes of a - core to be saved. Unit suffixes are allowed just as in - . + The maximum (compressed or uncompressed) size in bytes of a core to be saved. Unit + suffixes are allowed just as in . @@ -120,9 +116,8 @@ by core dumps might temporarily exceed these limits while core dumps are processed. Note that old core dumps are also removed based on time via - systemd-tmpfiles8. Set - either value to 0 to turn off size-based - clean-up. + systemd-tmpfiles8. + Set either value to 0 to turn off size-based cleanup. diff --git a/man/coredumpctl.xml b/man/coredumpctl.xml index 6ceed41b059..d45ed753b25 100644 --- a/man/coredumpctl.xml +++ b/man/coredumpctl.xml @@ -162,7 +162,7 @@ Show information of the most recent core dump only, instead of listing all known core - dumps. (Equivalent to + dumps. Equivalent to . diff --git a/man/os-release.xml b/man/os-release.xml index fb24eda1825..a7c60183aef 100644 --- a/man/os-release.xml +++ b/man/os-release.xml @@ -373,7 +373,7 @@ A lower-case string (mostly numeric, no spaces or other characters outside of 0–9, a–z, ".", "_" and "-") identifying the operating system extensions support level, to indicate which - extension images are supported. See: + extension images are supported. See systemd-sysext8) for more information. diff --git a/man/repart.d.xml b/man/repart.d.xml index 0305e255c77..d3059e9ec60 100644 --- a/man/repart.d.xml +++ b/man/repart.d.xml @@ -452,8 +452,8 @@ If the special value auto is specified, the source to copy from is automatically picked up from the running system (or the image specified with — if used). A partition that matches both the configured partition type (as - declared with Type= above), and the currently mounted directory appropriate for - that partition type is determined. For example, if the partition type is set to + declared with Type= described above), and the currently mounted directory + appropriate for that partition type is determined. For example, if the partition type is set to root the partition backing the root directory (/) is used as source to copy from — if its partition type is set to root as well. If the declared type is usr the partition backing /usr/ is used as @@ -529,7 +529,7 @@ MakeDirectories= - akes one or more absolute paths, separated by whitespace, each declaring a directory + Takes one or more absolute paths, separated by whitespace, each declaring a directory to create within the new file system. Behaviour is similar to CopyFiles=, but instead of copying in a set of files this just creates the specified directories with the default mode of 0755 owned by the root user and group, plus all their parent directories (with the same @@ -564,10 +564,10 @@ are copied in or the file system configured with Format= is created. The LUKS2 UUID is automatically derived from the partition UUID in a stable fashion. If - key-file or key-file+tpm2 is used a key is added to the LUKS2 - superblock, configurable with the switch to + key-file or key-file+tpm2 is used, a key is added to the LUKS2 + superblock, configurable with the option to systemd-repart. If tpm2 or key-file+tpm2 is - used a key is added to the LUKS2 superblock that is enrolled to the local TPM2 chip, as configured + used, a key is added to the LUKS2 superblock that is enrolled to the local TPM2 chip, as configured with the and options to systemd-repart. @@ -623,7 +623,7 @@ has no effect on explicit mounts, such as those done via mount8 or fstab5 + project='man-pages'>fstab5. If both bit 50 and 59 are set for a partition (i.e. the partition is marked both read-only and marked for file system growing) the latter is typically without effect: the read-only flag takes diff --git a/man/systemd-cryptenroll.xml b/man/systemd-cryptenroll.xml index d5719bc4635..c6d6c5bd6ca 100644 --- a/man/systemd-cryptenroll.xml +++ b/man/systemd-cryptenroll.xml @@ -84,7 +84,7 @@ URI Enroll a PKCS#11 security token or smartcard (e.g. a YubiKey). Expects a PKCS#11 - smart card URI referring to the token. Alternatively the special value auto may + smartcard URI referring to the token. Alternatively the special value auto may be specified, in order to automatically determine the URI of a currently plugged in security token (of which there must be exactly one). The special value list may be used to enumerate all suitable PKCS#11 tokens currently plugged in. The security token must contain an RSA diff --git a/man/systemd-firstboot.xml b/man/systemd-firstboot.xml index 87cf98c31a0..66d829941b8 100644 --- a/man/systemd-firstboot.xml +++ b/man/systemd-firstboot.xml @@ -307,7 +307,7 @@ passwd.shell.root - Specifies the shell binary to use for the specified account when creating it. + Specifies the shell binary to use for the specified account. Equivalent to the credential of the same name defined for the systemd-sysusers.service8 service. diff --git a/man/systemd-machine-id-setup.xml b/man/systemd-machine-id-setup.xml index a9c52d842c5..177fe892a65 100644 --- a/man/systemd-machine-id-setup.xml +++ b/man/systemd-machine-id-setup.xml @@ -90,7 +90,7 @@ - Takes a path to a device node or refular file as argument. This is similar to + Takes a path to a device node or regular file as argument. This is similar to as described above, but operates on a disk image instead of a directory tree. diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index e929d32f62b..3623ef015a1 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -1375,12 +1375,12 @@ After=sys-subsystem-net-devices-ens1.device The combination of the three operations above ensures that it is possible to log into the - host's user account inside the container as if it was local to the container. The user is only mapped - transiently, while the container is running and the mapping itself does not result in persistent - changes to the container (except maybe for generated log messages at login time, and similar). Note - that in particular the UID/GID assignment in the container is not made persistently. If the user is - mapped transiently, it is best to not allow the user to make persistent changes to the container. If - the user leaves files or directories owned by the user, and those UIDs/GIDs are recycled during later + container using the same account information as on the host. The user is only mapped transiently, + while the container is running, and the mapping itself does not result in persistent changes to the + container (except maybe for log messages generated at login time, and similar). Note that in + particular the UID/GID assignment in the container is not made persistently. If the user is mapped + transiently, it is best to not allow the user to make persistent changes to the container. If the + user leaves files or directories owned by the user, and those UIDs/GIDs are reused during later container invocations (possibly with a different mapping), those files and directories will be accessible to the "new" user. @@ -1581,9 +1581,9 @@ After=sys-subsystem-net-devices-ens1.device -b The above command line will invoke the specified image file image.raw in - volatile mode, i.e with an empty /etc/ and /var/, so that - the container's payload recognizes this as first boot condition, and will invoke - systemd-firstboot.service, which then read the two passed credentials to + volatile mode, i.e. with empty /etc/ and /var/. The + container payload will recognize this as a first boot, and will invoke + systemd-firstboot.service, which then reads the two passed credentials to configure the system's initial locale and root password. diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index 7dbbfa0001f..34c1257ab00 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -275,7 +275,7 @@ search foobar.com barbar.com fragility in both directions: a valid global name could be obscured by a local name, and resolution of a relative local name could suddenly break when a new top-level domain is created, or when a new subdomain of a top-level domain in registered. Resolving any given name as either relative or absolute - avoids this ambiguity.) + avoids this ambiguity. This resolver has a notion of the special .local domain used for MulticastDNS, and will not route queries with that suffix to unicast DNS servers unless explicitly diff --git a/man/systemd-sysext.xml b/man/systemd-sysext.xml index ad6a401c7a2..9d368f7958f 100644 --- a/man/systemd-sysext.xml +++ b/man/systemd-sysext.xml @@ -46,7 +46,7 @@ operating system tree. When one or more system extension images are activated, their /usr/ and /opt/ hierarchies are combined via overlayfs with the same hierarchies of the host OS, and the host - /usr/ and /opt overmounted with it ("merging"). When they are + /usr/ and /opt/ overmounted with it ("merging"). When they are deactivated, the mount point is disassembled — again revealing the unmodified original host version of the hierarchy ("unmerging"). Merging thus makes the extension's resources suddenly appear below the /usr/ and /opt/ hierarchies as if they were included in the @@ -127,13 +127,15 @@ Uses The primary use case for system images are immutable environments where debugging and development - tools shall optionally be made available, but not included in the immutable base OS image itself - (e.g. strace and gdb shall be an optionally installable - addition in order to make debugging/development easier). System extension images should not be - misunderstood as a generic software packaging framework, as no dependency scheme is available: system - extensions should carry all files they need themselves, except for those already shipped in the - underlying host system image. Typically, system extension images are built at the same time as the base - OS image — within the same build system. + tools shall optionally be made available, but not included in the immutable base OS image itself (e.g. + strace1 + and + gdb1 + shall be an optionally installable addition in order to make debugging/development easier). System + extension images should not be misunderstood as a generic software packaging framework, as no dependency + scheme is available: system extensions should carry all files they need themselves, except for those + already shipped in the underlying host system image. Typically, system extension images are built at the + same time as the base OS image — within the same build system. Another use case for the system extension concept is temporarily overriding OS supplied resources with newer ones, for example to install a locally compiled development version of some low-level diff --git a/man/systemd-system.conf.xml b/man/systemd-system.conf.xml index c11dd461439..5824e01e0c8 100644 --- a/man/systemd-system.conf.xml +++ b/man/systemd-system.conf.xml @@ -262,7 +262,7 @@ names in status messages (e.g. systemd-journald.service), instead of the longer and more informative descriptions set with Description= (e.g. Journal Logging Service). If , the system manager will use both unit names - and descriptions in status messages (e.g. systemdmd-jouranld.service - Journal Logging + and descriptions in status messages (e.g. systemd-journald.service - Journal Logging Service). See diff --git a/man/systemd-userdbd.service.xml b/man/systemd-userdbd.service.xml index fbbc740040f..84a3fc0452e 100644 --- a/man/systemd-userdbd.service.xml +++ b/man/systemd-userdbd.service.xml @@ -34,7 +34,7 @@ JSON user/group records from classic UNIX/glibc NSS user/group records in order to provide full backwards compatibility. It may also pick up statically defined JSON user/group records from drop-in files in /etc/userdb/, /run/userdb/, - /run/host/userdb/ and /use/lib/userdb/. + /run/host/userdb/ and /usr/lib/userdb/. Most of systemd-userdbd's functionality is accessible through the userdbctl1 diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index ccb1567900e..38f1cc59eec 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -402,14 +402,15 @@ ExtensionImages= This setting is similar to MountImages= in that it mounts a file - system hierarchy from a block device node or loopback file, but instead of providing a destination path, - an overlay will be set up. This option expects a whitespace separated list of mount definitions. Each - definition consists of a source path, optionally followed by a colon and a list of mount options. + system hierarchy from a block device node or loopback file, but instead of providing a destination + path, an overlay will be set up. This option expects a whitespace separated list of mount + definitions. Each definition consists of a source path, optionally followed by a colon and a list of + mount options. A read-only OverlayFS will be set up on top of /usr/ and - /opt/ hierarchies from the root. The order in which the images are listed - will determine the order in which the overlay is laid down: images specified first to last will result - in overlayfs layers bottom to top. + /opt/ hierarchies. The order in which the images are listed will determine the + order in which the overlay is laid down: images specified first to last will result in overlayfs + layers bottom to top. Mount options may be defined as a single comma-separated list of options, in which case they will be implicitly applied to the root partition on the image, or a series of colon-separated tuples @@ -2304,7 +2305,7 @@ SystemCallErrorNumber=EPERM Sets environment variables for executed processes. Each line is unquoted using the rules described in "Quoting" section in - systemd.syntax5 + systemd.syntax7 and becomes a list of variable assignments. If you need to assign a value containing spaces or the equals sign to a variable, put quotes around the whole assignment. Variable expansion is not performed inside the strings and the $ character has no special meaning. Specifier diff --git a/man/systemd.link.xml b/man/systemd.link.xml index 1093e2e0b84..ee4356ac3d6 100644 --- a/man/systemd.link.xml +++ b/man/systemd.link.xml @@ -457,7 +457,7 @@ MTUBytes= The maximum transmission unit in bytes to set for the - device. The usual suffixes K, M, G, are supported and are + device. The usual suffixes K, M, G are supported and are understood to the base of 1024. @@ -465,7 +465,7 @@ BitsPerSecond= The speed to set for the device, the value is rounded - down to the nearest Mbps. The usual suffixes K, M, G, are + down to the nearest Mbps. The usual suffixes K, M, G are supported and are understood to the base of 1000. @@ -788,7 +788,7 @@ GenericSegmentOffloadMaxBytes= Specifies the maximum size of a Generic Segment Offload (GSO) packet the - device should accept. The usual suffixes K, M, G, are supported and are + device should accept. The usual suffixes K, M, G are supported and are understood to the base of 1024. An unsigned integer in the range 1…65536. Defaults to unset. @@ -796,8 +796,8 @@ GenericSegmentOffloadMaxSegments= - Specifies the maximum number of a Generic Segment Offload (GSO) segments the device should - accept. An unsigned integer in the range 1…65535. Defaults to unset. + Specifies the maximum number of Generic Segment Offload (GSO) segments the device should + accept. An unsigned integer in the range 1…65535. Defaults to unset. diff --git a/man/systemd.netdev.xml b/man/systemd.netdev.xml index 1d1d71786fa..f62b4cb4004 100644 --- a/man/systemd.netdev.xml +++ b/man/systemd.netdev.xml @@ -390,7 +390,7 @@ DefaultPVID= This specifies the default port VLAN ID of a newly attached bridge port. - Set this to an integer in the range 1–4094 or none to disable the PVID. + Set this to an integer in the range 1…4094 or none to disable the PVID. @@ -460,7 +460,7 @@ Id= - The VLAN ID to use. An integer in the range 0–4094. + The VLAN ID to use. An integer in the range 0…4094. This setting is compulsory. @@ -654,7 +654,7 @@ TTL= A fixed Time To Live N on Virtual eXtensible Local Area Network packets. - Takes inherit or a number in the range 0–255. 0 is a special + Takes inherit or a number in the range 0…255. 0 is a special value meaning inherit the inner protocol's TTL value. inherit means that it will inherit the outer protocol's TTL value. @@ -913,7 +913,7 @@ TunnelId= - Specifies the tunnel identifier. Takes an number in the range 1–4294967295. The value used + Specifies the tunnel identifier. Takes an number in the range 1…4294967295. The value used must match the PeerTunnelId= value being used at the peer. This setting is compulsory. @@ -1002,7 +1002,7 @@ SessionId= - Specifies the session identifier. Takes an number in the range 1–4294967295. The value used + Specifies the session identifier. Takes an number in the range 1…4294967295. The value used must match the SessionId= value being used at the peer. This setting is compulsory. @@ -1010,7 +1010,7 @@ PeerSessionId= - Specifies the peer session identifier. Takes an number in the range 1–4294967295. + Specifies the peer session identifier. Takes an number in the range 1…4294967295. The value used must match the PeerSessionId= value being used at the peer. This setting is compulsory. @@ -1234,7 +1234,7 @@ TTL= A fixed Time To Live N on tunneled packets. N is a - number in the range 1–255. 0 is a special value meaning that + number in the range 1…255. 0 is a special value meaning that packets inherit the TTL value. The default value for IPv4 tunnels is 0 (inherit). The default value for IPv6 tunnels is 64. @@ -1256,7 +1256,7 @@ It is only used for IPv6 tunnels. A flow label of zero is used to indicate packets that have not been labeled. - It can be configured to a value in the range 0–0xFFFFF, or be + It can be configured to a value in the range 0…0xFFFFF, or be set to inherit, in which case the original flowlabel is used. @@ -1673,15 +1673,15 @@ Sets a comma-separated list of IP (v4 or v6) addresses with CIDR masks from which this peer is allowed to send incoming traffic and to which outgoing traffic for this peer is directed. + The catch-all 0.0.0.0/0 may be specified for matching all IPv4 addresses, and ::/0 may be specified for matching all IPv6 addresses. - Note that this only affects "routing inside the network interface itself", - as in, which wireguard peer packets with a specific destination address are sent to, - and what source addresses are accepted from which peer. - To cause packets to be sent via wireguard in first place, a route needs - to be added, as well - either in the [Routes] section on the - .network matching the wireguard interface, or outside of networkd. - + + Note that this only affects routing inside the network interface itself, + i.e. the packets that pass through the tunnel itself. To cause packets to be sent via the tunnel in + the first place, an appropriate route needs to be added as well — either in the + [Routes] section on the .network matching the wireguard + interface, or externally to systemd-networkd. @@ -1823,7 +1823,7 @@ AdUserPortKey= Specifies the 802.3ad user defined portion of the port key. Takes a number in the range - 0–1023. + 0…1023. @@ -2036,9 +2036,9 @@ [BatmanAdvanced] Section Options - The [BatmanAdvanced] section only applies for - netdevs of kind batadv and accepts the - following keys: + + The [BatmanAdvanced] section only applies for netdevs of kind batadv and accepts + the following keys: diff --git a/man/systemd.network.xml b/man/systemd.network.xml index 242d4ea0668..b8bb8aedf46 100644 --- a/man/systemd.network.xml +++ b/man/systemd.network.xml @@ -1423,7 +1423,7 @@ IPv6Token=prefixstable:2002:da8:1:: Metric= The metric of the route. Takes an unsigned integer in the range 0…4294967295. - Defaluts to unset, and the kernel's default will be used. + Defaults to unset, and the kernel's default will be used. @@ -1615,9 +1615,10 @@ IPv6Token=prefixstable:2002:da8:1:: SendHostname= When true (the default), the machine's hostname (or the value specified with - Hostname= below) will be sent to the DHCP server. Note that the hostname must - consist only of 7-bit ASCII lower-case characters and no spaces or dots, and be formatted as a - valid DNS domain name. Otherwise, the hostname is not sent even if this option is true. + Hostname=, described below) will be sent to the DHCP server. Note that the + hostname must consist only of 7-bit ASCII lower-case characters and no spaces or dots, and be + formatted as a valid DNS domain name. Otherwise, the hostname is not sent even if this option is + true. @@ -1911,8 +1912,8 @@ IPv6Token=prefixstable:2002:da8:1:: FallbackLeaseLifetimeSec= Allows to set DHCPv4 lease lifetime when DHCPv4 server does not send the lease lifetime. - Takes one of forever or infinity means that the address - never expires. Defaults to unset. + Takes one of forever or infinity. The latter means that the + address never expires. Defaults to unset. @@ -2339,9 +2340,9 @@ IPv6Token=prefixstable:2002:da8:1:: ServerAddress= Specifies server address for the DHCP server. Takes an IPv4 address with prefix - length, e.g., 192.168.0.1/24. This setting may be useful when the link which - DHCP server running on has multiple static addresses. When unset, one of static addresses in - the link will be automatically selected. Defaults to unset. + length, for example 192.168.0.1/24. This setting may be useful when the link on + which the DHCP server is running has multiple static addresses. When unset, one of static addresses + in the link will be automatically selected. Defaults to unset. @@ -2521,23 +2522,22 @@ IPv6Token=prefixstable:2002:da8:1:: [DHCPServerStaticLease] Section Options - The [DHCPServerStaticLease] section configures a static DHCP lease to - assign a pre-set IPv4 address to a specific device based on its MAC address. This section can be - specified multiple times. + The [DHCPServerStaticLease] section configures a static DHCP lease to assign a + fixed IPv4 address to a specific device based on its MAC address. This section can be specified multiple + times. MACAddress= - The hardware address of a device which should be assigned IPv4 address - specified in Address=. This key is mandatory. + The hardware address of a device to match. This key is mandatory. Address= - IPv4 address that should be assigned to a device with a hardware address - specified in MACAddress=. This key is mandatory. + The IPv4 address that should be assigned to the device that was matched with + MACAddress=. This key is mandatory. diff --git a/man/systemd.nspawn.xml b/man/systemd.nspawn.xml index 7ba8e361b42..dc0e2f9fd21 100644 --- a/man/systemd.nspawn.xml +++ b/man/systemd.nspawn.xml @@ -202,7 +202,7 @@ capabilities (see capabilities7 for details). The AmbientCapability= setting - specifies capability which will be passed to to started program + specifies capability which will be passed to the started program in the inheritable and ambient capability sets. This will grant these capabilities to this process. This setting correspond to the command line switch. diff --git a/man/systemd.preset.xml b/man/systemd.preset.xml index 64333a3216f..9e6db28536b 100644 --- a/man/systemd.preset.xml +++ b/man/systemd.preset.xml @@ -207,7 +207,7 @@ disable * systemd-delta1 - daemon8 + daemon7 has a discussion of packaging scriptlets. Fedora page introducing the use of presets: diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 350bc5f8e5b..884260a2159 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -1134,7 +1134,7 @@ \;. Each command line is unquoted using the rules described in "Quoting" section in - systemd.syntax5. The + systemd.syntax7. The first item becomes the command to execute, and the subsequent items the arguments. This syntax is inspired by shell syntax, but only the meta-characters and expansions diff --git a/man/systemd.unit.xml b/man/systemd.unit.xml index 9a4010c4527..b6e4a2233c4 100644 --- a/man/systemd.unit.xml +++ b/man/systemd.unit.xml @@ -1535,7 +1535,7 @@ ConditionControlGroupController= - Check whether given cgroup controllers (eg. cpu) are available + Check whether given cgroup controllers (e.g. cpu) are available for use on the system or whether the legacy v1 cgroup or the modern v2 cgroup hierarchy is used. diff --git a/man/userdbctl.xml b/man/userdbctl.xml index 0871306b202..611c425b795 100644 --- a/man/userdbctl.xml +++ b/man/userdbctl.xml @@ -42,7 +42,7 @@ url="https://systemd.io/USER_GROUP_API">User/Group Record Lookup API via Varlink, and may also pick up drop-in JSON user and group records from /etc/userdb/, /run/userdb/, /run/host/userdb/, - /use/lib/userdb/. + /usr/lib/userdb/. @@ -104,7 +104,7 @@ Controls whether to include user/group lookups in the output that are defined using drop-in files in /etc/userdb/, /run/userdb/, - /run/host/userdb/, /use/lib/userdb/. If + /run/host/userdb/, /usr/lib/userdb/. If is used these records are suppressed. If is specified such users/groups are included in the output (which is the default). @@ -260,7 +260,7 @@ systemd-userdbd.service8 and picks up JSON user/group records from /etc/userdb/, /run/userdb/, /run/host/userdb/, - /use/lib/userdb/. + /usr/lib/userdb/. -- 2.39.2