diff --git a/man/bootup.xml b/man/bootup.xml index 5770e7828d2..26f762bf816 100644 --- a/man/bootup.xml +++ b/man/bootup.xml @@ -32,7 +32,7 @@ of firmware, this firmware may also load the kernel directly. The kernel (optionally) mounts an in-memory file system, often generated by - dracut8, + dracut8, which looks for the root file system. Nowadays this is usually implemented as an initramfs — a compressed archive which is extracted when the kernel boots up into a lightweight in-memory file system based on tmpfs, but in the past normal file systems using an in-memory block device (ramdisk) were used, and the @@ -349,7 +349,7 @@ systemd-reboot.service systemd-poweroff.service systemd-halt.service syste systemd.special7, systemd.target5, systemd-halt.service8, - dracut8 + dracut8 diff --git a/man/coredumpctl.xml b/man/coredumpctl.xml index ab5dffdfb37..a3136113694 100644 --- a/man/coredumpctl.xml +++ b/man/coredumpctl.xml @@ -134,7 +134,7 @@ Invoke a debugger on the last core dump matching specified characteristics. By default, - gdb1 + gdb1 will be used. This may be changed using the option or the $SYSTEMD_DEBUGGER environment variable. @@ -213,7 +213,7 @@ Use the given debugger for the debug command. If not given and $SYSTEMD_DEBUGGER is unset, then - gdb1 + gdb1 will be used. diff --git a/man/journalctl.xml b/man/journalctl.xml index 6e4728b0134..5c32ce8b9b3 100644 --- a/man/journalctl.xml +++ b/man/journalctl.xml @@ -621,7 +621,7 @@ Filter output to entries where the MESSAGE= field matches the specified regular expression. PERL-compatible regular expressions are used, see - pcre2pattern3 + pcre2pattern3 for a detailed description of the syntax. If the pattern is all lowercase, matching is case insensitive. diff --git a/man/kernel-command-line.xml b/man/kernel-command-line.xml index 52939deec0b..9627f7e14b8 100644 --- a/man/kernel-command-line.xml +++ b/man/kernel-command-line.xml @@ -109,7 +109,7 @@ During early boot, the generation of core dump files is disabled until a core dump handler (if any) takes over. This parameter allows specifying an absolute path where core dump files should be stored until a handler is installed. The path should be absolute and may contain specifiers, see - core5 for details. + core5 for details. diff --git a/man/kernel-install.xml b/man/kernel-install.xml index 34bb5d2f1ed..3df80751dd2 100644 --- a/man/kernel-install.xml +++ b/man/kernel-install.xml @@ -80,7 +80,7 @@ 50-depmod.install runs - depmod8 for the + depmod8 for the KERNEL-VERSION. 90-loaderentry.install copies KERNEL-IMAGE @@ -231,7 +231,7 @@ machine-id5, os-release5, - depmod8, + depmod8, systemd-boot7, Boot Loader Specification diff --git a/man/networkctl.xml b/man/networkctl.xml index a6bc61a44fc..bd958fb1e01 100644 --- a/man/networkctl.xml +++ b/man/networkctl.xml @@ -233,7 +233,7 @@ s - Service VLAN, m - Two-port MAC Relay (TPMR) Show numerical address labels that can be used for address selection. This is the same information that - ip-addrlabel8 + ip-addrlabel8 shows. See RFC 3484 for a discussion of address labels. diff --git a/man/org.freedesktop.LogControl1.xml b/man/org.freedesktop.LogControl1.xml index 125a008347d..385e2903120 100644 --- a/man/org.freedesktop.LogControl1.xml +++ b/man/org.freedesktop.LogControl1.xml @@ -75,7 +75,7 @@ node /org/freedesktop/LogControl1 { Properties LogLevel describes the - syslog3-style + syslog3-style log-level, and should be one of emerg, alert, crit, err, warning, notice, info, debug, in order of increasing verbosity. @@ -86,14 +86,14 @@ node /org/freedesktop/LogControl1 { journal (log the the journal natively, see systemd-journald.service8), syslog (log using the - syslog3 call). + syslog3 call). Those two properties are writable, so they may be set by sufficiently privileged users. SyslogIdentifier is a read-only property that shows the "syslog identifier". It is a short string that identifies the program that is the source of log messages that is passed to - the syslog3 call. + the syslog3 call. Note: journalctl option / may diff --git a/man/org.freedesktop.home1.xml b/man/org.freedesktop.home1.xml index 1b2c52af039..f65ef33f216 100644 --- a/man/org.freedesktop.home1.xml +++ b/man/org.freedesktop.home1.xml @@ -165,7 +165,7 @@ node /org/freedesktop/home1 { GetHomeByName() returns basic user information (a minimal subset of the full user record), provided a user name. The information supplied more or less matches what - getpwnam3 returns: + getpwnam3 returns: the numeric UID and GID, the real name, home directory and shell. In addition it returns a state identifier describing the state the user's home directory is in, as well as a bus path referring to the bus object encapsulating the user record and home directory. This object implements the diff --git a/man/org.freedesktop.import1.xml b/man/org.freedesktop.import1.xml index 1414cc15d79..56ce9f0b450 100644 --- a/man/org.freedesktop.import1.xml +++ b/man/org.freedesktop.import1.xml @@ -37,7 +37,7 @@ is mostly a small companion service for systemd-machined.service8. Many operations to manipulate local container and VM images are hence available via the systemd-machined D-Bus API, c.f. - org.freedesktop.machine1.service5. + org.freedesktop.machine15. diff --git a/man/org.freedesktop.login1.xml b/man/org.freedesktop.login1.xml index 0292288d3a6..1b7c3b64213 100644 --- a/man/org.freedesktop.login1.xml +++ b/man/org.freedesktop.login1.xml @@ -567,7 +567,7 @@ node /org/freedesktop/login1 { SetWallMessage() sets the wall message (the message that will be sent out to all terminals and stored in a - utmp5 record) for a + utmp5 record) for a subsequent scheduled shutdown operation. The parameter wall_message specifies the shutdown reason (and may be empty) which will be included in the shutdown message. The parameter enable specifies whether to print a wall message on shutdown. diff --git a/man/org.freedesktop.machine1.xml b/man/org.freedesktop.machine1.xml index c18e133e7cb..a54fa040b26 100644 --- a/man/org.freedesktop.machine1.xml +++ b/man/org.freedesktop.machine1.xml @@ -368,7 +368,8 @@ node /org/freedesktop/machine1 { OpenMachinePTY() allocates a pseudo TTY in the container and returns a file descriptor and its path. This is equivalent to transitioning into the container and invoking - posix_openpt3. + posix_openpt3. + OpenMachineLogin() allocates a pseudo TTY in the container and ensures that a getty login prompt of the container is running on the other end. It returns the file descriptor of diff --git a/man/org.freedesktop.systemd1.xml b/man/org.freedesktop.systemd1.xml index b6a643aaf1b..8e3c7611a87 100644 --- a/man/org.freedesktop.systemd1.xml +++ b/man/org.freedesktop.systemd1.xml @@ -1312,7 +1312,7 @@ node /org/freedesktop/systemd1 { SetUnitProperties() may be used to modify certain unit properties at runtime. Not all properties may be changed at runtime, but many resource management settings (primarily those listed in - systemd.cgroup5) + systemd.resource-control5) may. The changes are applied instantly and stored on disk for future boots, unless runtime is true, in which case the settings only apply until the next reboot. name is the name of the unit to modify. properties are @@ -8278,16 +8278,16 @@ node /org/freedesktop/systemd1/unit/dev_2dsda3_2eswap { Most of the properties map directly to the corresponding settings in swap unit files. As mount units invoke the - swapon8 command, + swapon8 command, their bus objects include implicit ExecActivate (and similar) fields which contain information about processes to execute. They also share most of the fields related to the execution context that Service objects expose (see above). In addition to these properties there are the following: ControlPID contains the PID of the currently running - swapon8 or - swapoff8 command if - there is one running, otherwise 0. + swapon8 or + swapoff8 + command if there is one running, otherwise 0. Result contains a value explaining why a mount unit failed if it failed. It can take the values success, resources, diff --git a/man/pam_systemd.xml b/man/pam_systemd.xml index 70927d73742..cf9ba71adcb 100644 --- a/man/pam_systemd.xml +++ b/man/pam_systemd.xml @@ -253,7 +253,7 @@ See systemd.resource-control5 for more information about the resources. - Also, see pam_set_data3 for additional information about how to set + Also, see pam_set_data3 for additional information about how to set the context objects. diff --git a/man/resolvectl.xml b/man/resolvectl.xml index e2d00b9cf08..0ae70dc34bd 100644 --- a/man/resolvectl.xml +++ b/man/resolvectl.xml @@ -316,11 +316,11 @@ Registers per-interface DNS configuration data with systemd-resolved. Expects a network interface name as only command line argument. Reads - resolv.conf5 compatible DNS - configuration data from its standard input. Relevant fields are nameserver and + resolv.conf5-compatible + DNS configuration data from its standard input. Relevant fields are nameserver and domain/search. This command is mostly identical to invoking - resolvectl with a combination of and - commands. + resolvectl with a combination of and + commands. diff --git a/man/sd-bus.xml b/man/sd-bus.xml index 0938255d5c0..199a4a81e99 100644 --- a/man/sd-bus.xml +++ b/man/sd-bus.xml @@ -86,6 +86,10 @@ sd_bus_get_name_machine_id3, sd_bus_get_name_creds3, sd_bus_get_owner_creds3, +sd_bus_get_property3, +sd_bus_get_property_trivial3, +sd_bus_get_property_string3, +sd_bus_get_property_strv3, sd_bus_get_scope3, sd_bus_get_tid3, sd_bus_get_unique_name3, @@ -111,10 +115,6 @@ sd_bus_message_get_errno3, sd_bus_message_get_error3, sd_bus_message_get_monotonic_usec3, -sd_bus_message_get_property3, -sd_bus_message_get_property_trivial3, -sd_bus_message_get_property_string3, -sd_bus_message_get_property_strv3, sd_bus_message_get_sender3, sd_bus_message_get_signature3, sd_bus_message_get_type3, diff --git a/man/sd_bus_interface_name_is_valid.xml b/man/sd_bus_interface_name_is_valid.xml index 73c0ba1bf1f..a72024e5a7e 100644 --- a/man/sd_bus_interface_name_is_valid.xml +++ b/man/sd_bus_interface_name_is_valid.xml @@ -91,7 +91,7 @@ systemd1, sd-bus3, - sd_bus_message_call_method3 + sd_bus_call_method3 diff --git a/man/sd_bus_message_get_type.xml b/man/sd_bus_message_get_type.xml index 2b962413d2a..442c763a492 100644 --- a/man/sd_bus_message_get_type.xml +++ b/man/sd_bus_message_get_type.xml @@ -83,11 +83,11 @@ SD_BUS_MESSAGE_METHOD_RETURN, SD_BUS_MESSAGE_METHOD_ERROR, SD_BUS_MESSAGE_SIGNAL. This type is either specified as a parameter when the message is created using - sd_bus_set_message_new3, + sd_bus_message_new3, or is set automatically when the message is created using - sd_bus_set_message_new_signal3, - sd_bus_set_message_new_method_call3, - sd_bus_set_message_new_method_error3 + sd_bus_message_new_signal3, + sd_bus_message_new_method_call3, + sd_bus_message_new_method_error3 and similar functions. sd_bus_message_get_error() returns the error stored in the message @@ -108,20 +108,20 @@ signal message. If interface is non-null, it also checks if the message has the same interface set. If member is non-null, it also checks if the message has the same member set. Also see - sd_bus_set_message_new_signal3. + sd_bus_message_new_signal3. It returns true when all checks pass. sd_bus_message_is_method_call() checks if message m is a method call message. If interface is non-null, it also checks if the message has the same interface set. If member is non-null, it also checks if the message has the same member set. Also see - sd_bus_set_message_new_method_call3. + sd_bus_message_new_method_call3. It returns true when all checks pass. sd_bus_message_is_method_error() checks if message m is an error reply message. If name is non-null, it also checks if the message has the same error identifier set. Also see - sd_bus_set_message_new_method_error3. + sd_bus_message_new_method_error3. It returns true when all checks pass. diff --git a/man/sd_bus_message_new_method_error.xml b/man/sd_bus_message_new_method_error.xml index 0c471c534ff..aa29007c27e 100644 --- a/man/sd_bus_message_new_method_error.xml +++ b/man/sd_bus_message_new_method_error.xml @@ -98,7 +98,7 @@ an error reply similarly to sd_bus_message_new_method_error(), but in addition to the error structure p, it takes an - errno3 + errno3 error value in parameter error. If the error p is set (see sd_bus_error_is_set3), @@ -111,7 +111,7 @@ The sd_bus_message_new_method_errnof() function creates an error reply similarly to sd_bus_message_new_method_error(). It takes an - errno3 + errno3 error value in parameter error, plus a printf3 format string format and corresponding arguments. diff --git a/man/sd_bus_message_new_signal.xml b/man/sd_bus_message_new_signal.xml index 97afcd5c591..5ac35e7a3a6 100644 --- a/man/sd_bus_message_new_signal.xml +++ b/man/sd_bus_message_new_signal.xml @@ -45,7 +45,7 @@ parameter. The signal will be sent to path path, on the interface interface, member member. When this message is sent, no reply is expected. See - sd_bus_message_new_call1 + sd_bus_message_new_method_call1 for a short description of the meaning of the path, interface, and member parameters. diff --git a/man/sd_bus_negotiate_fds.xml b/man/sd_bus_negotiate_fds.xml index f17a54f2694..340049fc972 100644 --- a/man/sd_bus_negotiate_fds.xml +++ b/man/sd_bus_negotiate_fds.xml @@ -152,7 +152,7 @@ systemd1, sd-bus3, sd_bus_start3, - sd_bus_message_can_send3, + sd_bus_can_send3, sd_bus_message_get_monotonic_usec3, sd_bus_message_get_realtime_usec3, sd_bus_message_get_seqnum3, diff --git a/man/sd_bus_reply_method_error.xml b/man/sd_bus_reply_method_error.xml index 0a85557ec6e..dcf9ee299fb 100644 --- a/man/sd_bus_reply_method_error.xml +++ b/man/sd_bus_reply_method_error.xml @@ -84,7 +84,7 @@ The sd_bus_reply_method_error() function sends an error reply to the call message. The error structure e specifies the error to send, and is used as described in - sd_bus_message_new_error3. + sd_bus_message_new_method_error3. If no reply is expected to call, this function succeeds without sending a reply. diff --git a/man/sd_bus_set_watch_bind.xml b/man/sd_bus_set_watch_bind.xml index cbdc7dd1eda..5638cdc0a62 100644 --- a/man/sd_bus_set_watch_bind.xml +++ b/man/sd_bus_set_watch_bind.xml @@ -48,7 +48,7 @@ socket binding for a bus connection object. If the b is true, the feature is enabled, otherwise disabled (which is the default). When enabled, and the selected bus address refers to an AF_UNIX socket in the file system which does not exist while the connection attempt is made an - inotify7 watch is installed on + inotify7 watch is installed on it, waiting for the socket to appear. As soon as the socket appears the connection is made. This functionality is useful in particular in early-boot programs that need to run before the system bus is available, but want to connect to it the instant it may be connected to. @@ -56,18 +56,18 @@ sd_bus_get_watch_bind() may be used to query the current setting of this feature. It returns zero when the feature is disabled, and positive if enabled. - Note that no timeout is applied while it is waited for the socket to appear. This means that any synchronous - remote operation (such as + Note that no timeout is applied while we wait for the socket to appear. This means that any + synchronous remote operation (such as sd_bus_call3, sd_bus_add_match3 or - sd_bus_request_name3), that is - used on a connection with this feature enabled that is not established yet might block unbounded if the socket is - never created. However, asynchronous remote operations (such as + sd_bus_request_name3), + that is used on a connection with this feature enabled that hasn't been established yet, might block + forever if the socket is never created. However, asynchronous remote operations (such as sd_bus_send3, - sd_bus_add_match_async3 or - sd_bus_request_match_async3) do - not block in this case, and safely enqueue the requested operations to be dispatched the instant the connection is - set up. + sd_bus_call_async3, + sd_bus_add_match_async3) + do not block in this case, and safely enqueue the requested operations to be dispatched the instant the + connection is set up. Use sd_bus_is_ready3 to determine whether the connection is fully established, i.e. whether the peer socket has been bound, connected to @@ -106,7 +106,7 @@ systemd1, sd-bus3, - inotify7, + inotify7, sd_bus_call3, sd_bus_add_match3, sd_bus_request_name3, diff --git a/man/sd_hwdb_get.xml b/man/sd_hwdb_get.xml index ded87215379..1372f4d80cd 100644 --- a/man/sd_hwdb_get.xml +++ b/man/sd_hwdb_get.xml @@ -148,7 +148,7 @@ systemd1, - systemd-udev.service8, + systemd-udevd.service8, sd-hwdb3, systemd-hwdb8 diff --git a/man/sd_hwdb_new.xml b/man/sd_hwdb_new.xml index 257b347b9b6..8f1c01b7314 100644 --- a/man/sd_hwdb_new.xml +++ b/man/sd_hwdb_new.xml @@ -112,7 +112,7 @@ systemd1, - systemd-udev.service8, + systemd-udevd.service8, sd-hwdb3, systemd-hwdb3 diff --git a/man/sysctl.d.xml b/man/sysctl.d.xml index dc10776e996..d26f82475b8 100644 --- a/man/sysctl.d.xml +++ b/man/sysctl.d.xml @@ -63,7 +63,7 @@ key.pattern.overridden.with.glob = custom net.ipv4.conf.enp3s0/200.forwarding or net/ipv4/conf/enp3s0.200/forwarding may be used to refer to /proc/sys/net/ipv4/conf/enp3s0.200/forwarding. A glob - glob7 pattern may be + glob7 pattern may be used to write the same value to all matching keys. Keys for which an explicit pattern exists will be excluded from any glob matching. In addition, a key may be explicitly excluded from being set by any matching glob patterns by specifying the key name prefixed with a - character and not diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml index 1106c36d0c8..ba8e67dff4c 100644 --- a/man/systemd-analyze.xml +++ b/man/systemd-analyze.xml @@ -669,7 +669,7 @@ Service b@0.service not loaded, b.socket cannot be started. dot command (see above), this selects which relationships are shown in the dependency graph. Both options require a - glob7 + glob7 pattern as an argument, which will be matched against the left-hand and the right-hand, respectively, nodes of a relationship. diff --git a/man/systemd-journald.service.xml b/man/systemd-journald.service.xml index f4ce4e4fe20..6b7a0bc4b99 100644 --- a/man/systemd-journald.service.xml +++ b/man/systemd-journald.service.xml @@ -106,18 +106,19 @@ systemd-tmpfiles --create --prefix /var/log/journal 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. To mitigate this issue, - systemd service manager explicitly turns off the SIGPIPE signal for all invoked processes by - default (this may be changed for each unit individually via the IgnoreSIGPIPE= option, see + signal7. + To mitigate this issue, systemd service manager explicitly turns off the SIGPIPE + signal for all invoked processes by default (this may be changed for each unit individually via the + IgnoreSIGPIPE= option, see systemd.exec5 for - details). After the standard output/standard error streams have been terminated they may not be recovered until the - services they are associated with are restarted. Note that during normal operation, - systemd-journald.service stores copies of the file descriptors for those streams in the - service manager. If systemd-journald.service is restarted using systemctl - restart or equivalent operation instead of a pair of separate systemctl stop and - systemctl start commands (or equivalent operations), these stream connections are not terminated - and survive the restart. It is thus safe to restart systemd-journald.service, but stopping it - is not recommended. + details). After the standard output/standard error streams have been terminated they may not be recovered + until the services they are associated with are restarted. Note that during normal operation, + systemd-journald.service stores copies of the file descriptors for those streams in + the service manager. If systemd-journald.service is restarted using + systemctl restart or equivalent operation instead of a pair of separate + systemctl stop and systemctl start commands (or equivalent + operations), these stream connections are not terminated and survive the restart. It is thus safe to + restart systemd-journald.service, but stopping it is not recommended. Note that the log record metadata for records transferred via such standard output/error streams reflect the metadata of the peer the stream was originally created for. If the stream connection is passed on to other diff --git a/man/systemd-machined.service.xml b/man/systemd-machined.service.xml index ab58d8fd3f7..5172f6511a9 100644 --- a/man/systemd-machined.service.xml +++ b/man/systemd-machined.service.xml @@ -76,7 +76,7 @@ The sd-bus3 library exposes the - sd_bus_open_system_container3 + sd_bus_open_system_machine3 call to connect to the system bus of any registered container. The diff --git a/man/systemd-network-generator.service.xml b/man/systemd-network-generator.service.xml index fcb3c69ffbf..4a3f78a9e57 100644 --- a/man/systemd-network-generator.service.xml +++ b/man/systemd-network-generator.service.xml @@ -96,7 +96,7 @@ systemd1, systemd-networkd.service8, - dracut8 + dracut8 diff --git a/man/systemd-networkd.service.xml b/man/systemd-networkd.service.xml index 94a7bfd5ef6..2913bb953df 100644 --- a/man/systemd-networkd.service.xml +++ b/man/systemd-networkd.service.xml @@ -92,7 +92,7 @@ systemd.network5, systemd.netdev5, systemd-networkd-wait-online.service8, - systemd-networkd-generator.service8 + systemd-network-generator.service8 diff --git a/man/systemd.exec.xml b/man/systemd.exec.xml index c828109d01a..64799edd99b 100644 --- a/man/systemd.exec.xml +++ b/man/systemd.exec.xml @@ -732,9 +732,9 @@ CapabilityBoundingSet=~CAP_B CAP_C kernel default of private-anonymous shared-anonymous elf-headers private-huge). See - core5 for the - meaning of the mapping types. When specified multiple times, all specified masks are ORed. When not - set, or if the empty value is assigned, the inherited value is not changed. + core5 + for the meaning of the mapping types. When specified multiple times, all specified masks are + ORed. When not set, or if the empty value is assigned, the inherited value is not changed. Add DAX pages to the dump filter @@ -880,7 +880,7 @@ CapabilityBoundingSet=~CAP_B CAP_C in NUMAMask=. For more details on each policy please see, set_mempolicy2. For overall overview of NUMA support in Linux see, - numa7 + numa7 diff --git a/man/systemd.link.xml b/man/systemd.link.xml index 7e17bf095fe..d7724a0a59c 100644 --- a/man/systemd.link.xml +++ b/man/systemd.link.xml @@ -27,7 +27,7 @@ Description A plain ini-style text file that encodes configuration for matching network devices, used by - systemd-udev8 and in + systemd-udevd8 and in particular its net_setup_link builtin. See systemd.syntax5 for a general description of the syntax. diff --git a/man/systemd.service.xml b/man/systemd.service.xml index a4a49f39af2..61484d530c4 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -1078,8 +1078,8 @@ manager. If set to kill and one of the service's processes is killed by the OOM killer the kernel is instructed to kill all remaining processes of the service, too. Defaults to the setting DefaultOOMPolicy= in - system.conf5 is - set to, except for services where Delegate= is turned on, where it defaults to + systemd-system.conf5 + is set to, except for services where Delegate= is turned on, where it defaults to continue. Use the OOMScoreAdjust= setting to configure whether processes of the unit