diff options
Diffstat (limited to 'man')
| -rw-r--r-- | man/org.freedesktop.import1.xml | 2 | ||||
| -rw-r--r-- | man/org.freedesktop.systemd1.xml | 2 | ||||
| -rw-r--r-- | man/sd-bus.xml | 8 | ||||
| -rw-r--r-- | man/sd_bus_interface_name_is_valid.xml | 2 | ||||
| -rw-r--r-- | man/sd_bus_message_get_type.xml | 14 | ||||
| -rw-r--r-- | man/sd_bus_message_new_signal.xml | 2 | ||||
| -rw-r--r-- | man/sd_bus_negotiate_fds.xml | 2 | ||||
| -rw-r--r-- | man/sd_bus_reply_method_error.xml | 2 | ||||
| -rw-r--r-- | man/sd_bus_set_watch_bind.xml | 4 | ||||
| -rw-r--r-- | man/sd_hwdb_get.xml | 2 | ||||
| -rw-r--r-- | man/sd_hwdb_new.xml | 2 | ||||
| -rw-r--r-- | man/systemd-machined.service.xml | 2 | ||||
| -rw-r--r-- | man/systemd-networkd.service.xml | 2 | ||||
| -rw-r--r-- | man/systemd.link.xml | 2 | ||||
| -rw-r--r-- | man/systemd.service.xml | 4 |
15 files changed, 26 insertions, 26 deletions
diff --git a/man/org.freedesktop.import1.xml b/man/org.freedesktop.import1.xml index 1414cc15d7..56ce9f0b45 100644 --- a/man/org.freedesktop.import1.xml +++ b/man/org.freedesktop.import1.xml @@ -37,7 +37,7 @@ is mostly a small companion service for <citerefentry><refentrytitle>systemd-machined.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>. Many operations to manipulate local container and VM images are hence available via the <command>systemd-machined</command> D-Bus API, c.f. - <citerefentry><refentrytitle>org.freedesktop.machine1.service</refentrytitle><manvolnum>5</manvolnum></citerefentry>. + <citerefentry><refentrytitle>org.freedesktop.machine1</refentrytitle><manvolnum>5</manvolnum></citerefentry>. </para> </refsect1> diff --git a/man/org.freedesktop.systemd1.xml b/man/org.freedesktop.systemd1.xml index c2d4c34cd5..8e3c7611a8 100644 --- a/man/org.freedesktop.systemd1.xml +++ b/man/org.freedesktop.systemd1.xml @@ -1312,7 +1312,7 @@ node /org/freedesktop/systemd1 { <para><function>SetUnitProperties()</function> 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 - <citerefentry><refentrytitle>systemd.cgroup</refentrytitle><manvolnum>5</manvolnum></citerefentry>) + <citerefentry><refentrytitle>systemd.resource-control</refentrytitle><manvolnum>5</manvolnum></citerefentry>) may. The changes are applied instantly and stored on disk for future boots, unless <varname>runtime</varname> is true, in which case the settings only apply until the next reboot. <varname>name</varname> is the name of the unit to modify. <varname>properties</varname> are diff --git a/man/sd-bus.xml b/man/sd-bus.xml index 0938255d5c..199a4a81e9 100644 --- a/man/sd-bus.xml +++ b/man/sd-bus.xml @@ -86,6 +86,10 @@ <citerefentry><refentrytitle>sd_bus_get_name_machine_id</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_get_name_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_get_owner_creds</refentrytitle><manvolnum>3</manvolnum></citerefentry>, +<citerefentry><refentrytitle>sd_bus_get_property</refentrytitle><manvolnum>3</manvolnum></citerefentry>, +<citerefentry><refentrytitle>sd_bus_get_property_trivial</refentrytitle><manvolnum>3</manvolnum></citerefentry>, +<citerefentry><refentrytitle>sd_bus_get_property_string</refentrytitle><manvolnum>3</manvolnum></citerefentry>, +<citerefentry><refentrytitle>sd_bus_get_property_strv</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_get_scope</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_get_tid</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_get_unique_name</refentrytitle><manvolnum>3</manvolnum></citerefentry>, @@ -111,10 +115,6 @@ <citerefentry><refentrytitle>sd_bus_message_get_errno</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_message_get_error</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_message_get_monotonic_usec</refentrytitle><manvolnum>3</manvolnum></citerefentry>, -<citerefentry><refentrytitle>sd_bus_message_get_property</refentrytitle><manvolnum>3</manvolnum></citerefentry>, -<citerefentry><refentrytitle>sd_bus_message_get_property_trivial</refentrytitle><manvolnum>3</manvolnum></citerefentry>, -<citerefentry><refentrytitle>sd_bus_message_get_property_string</refentrytitle><manvolnum>3</manvolnum></citerefentry>, -<citerefentry><refentrytitle>sd_bus_message_get_property_strv</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_message_get_sender</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_message_get_signature</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_message_get_type</refentrytitle><manvolnum>3</manvolnum></citerefentry>, diff --git a/man/sd_bus_interface_name_is_valid.xml b/man/sd_bus_interface_name_is_valid.xml index 73c0ba1bf1..a72024e5a7 100644 --- a/man/sd_bus_interface_name_is_valid.xml +++ b/man/sd_bus_interface_name_is_valid.xml @@ -91,7 +91,7 @@ <para> <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>, - <citerefentry><refentrytitle>sd_bus_message_call_method</refentrytitle><manvolnum>3</manvolnum></citerefentry> + <citerefentry><refentrytitle>sd_bus_call_method</refentrytitle><manvolnum>3</manvolnum></citerefentry> </para> </refsect1> diff --git a/man/sd_bus_message_get_type.xml b/man/sd_bus_message_get_type.xml index 2b962413d2..442c763a49 100644 --- a/man/sd_bus_message_get_type.xml +++ b/man/sd_bus_message_get_type.xml @@ -83,11 +83,11 @@ <constant>SD_BUS_MESSAGE_METHOD_RETURN</constant>, <constant>SD_BUS_MESSAGE_METHOD_ERROR</constant>, <constant>SD_BUS_MESSAGE_SIGNAL</constant>. This type is either specified as a parameter when the message is created using - <citerefentry><refentrytitle>sd_bus_set_message_new</refentrytitle><manvolnum>3</manvolnum></citerefentry>, + <citerefentry><refentrytitle>sd_bus_message_new</refentrytitle><manvolnum>3</manvolnum></citerefentry>, or is set automatically when the message is created using - <citerefentry><refentrytitle>sd_bus_set_message_new_signal</refentrytitle><manvolnum>3</manvolnum></citerefentry>, - <citerefentry><refentrytitle>sd_bus_set_message_new_method_call</refentrytitle><manvolnum>3</manvolnum></citerefentry>, - <citerefentry><refentrytitle>sd_bus_set_message_new_method_error</refentrytitle><manvolnum>3</manvolnum></citerefentry> + <citerefentry><refentrytitle>sd_bus_message_new_signal</refentrytitle><manvolnum>3</manvolnum></citerefentry>, + <citerefentry><refentrytitle>sd_bus_message_new_method_call</refentrytitle><manvolnum>3</manvolnum></citerefentry>, + <citerefentry><refentrytitle>sd_bus_message_new_method_error</refentrytitle><manvolnum>3</manvolnum></citerefentry> and similar functions.</para> <para><function>sd_bus_message_get_error()</function> returns the error stored in the message @@ -108,20 +108,20 @@ signal message. If <parameter>interface</parameter> is non-null, it also checks if the message has the same interface set. If <parameter>member</parameter> is non-null, it also checks if the message has the same member set. Also see - <citerefentry><refentrytitle>sd_bus_set_message_new_signal</refentrytitle><manvolnum>3</manvolnum></citerefentry>. + <citerefentry><refentrytitle>sd_bus_message_new_signal</refentrytitle><manvolnum>3</manvolnum></citerefentry>. It returns true when all checks pass.</para> <para><function>sd_bus_message_is_method_call()</function> checks if message <parameter>m</parameter> is a method call message. If <parameter>interface</parameter> is non-null, it also checks if the message has the same interface set. If <parameter>member</parameter> is non-null, it also checks if the message has the same member set. Also see - <citerefentry><refentrytitle>sd_bus_set_message_new_method_call</refentrytitle><manvolnum>3</manvolnum></citerefentry>. + <citerefentry><refentrytitle>sd_bus_message_new_method_call</refentrytitle><manvolnum>3</manvolnum></citerefentry>. It returns true when all checks pass.</para> <para><function>sd_bus_message_is_method_error()</function> checks if message <parameter>m</parameter> is an error reply message. If <parameter>name</parameter> is non-null, it also checks if the message has the same error identifier set. Also see - <citerefentry><refentrytitle>sd_bus_set_message_new_method_error</refentrytitle><manvolnum>3</manvolnum></citerefentry>. + <citerefentry><refentrytitle>sd_bus_message_new_method_error</refentrytitle><manvolnum>3</manvolnum></citerefentry>. It returns true when all checks pass.</para> </refsect1> diff --git a/man/sd_bus_message_new_signal.xml b/man/sd_bus_message_new_signal.xml index 97afcd5c59..5ac35e7a3a 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 <parameter>path</parameter>, on the interface <parameter>interface</parameter>, member <parameter>member</parameter>. When this message is sent, no reply is expected. See - <citerefentry><refentrytitle>sd_bus_message_new_call</refentrytitle><manvolnum>1</manvolnum></citerefentry> + <citerefentry><refentrytitle>sd_bus_message_new_method_call</refentrytitle><manvolnum>1</manvolnum></citerefentry> for a short description of the meaning of the <parameter>path</parameter>, <parameter>interface</parameter>, and <parameter>member</parameter> parameters. </para> diff --git a/man/sd_bus_negotiate_fds.xml b/man/sd_bus_negotiate_fds.xml index f17a54f269..340049fc97 100644 --- a/man/sd_bus_negotiate_fds.xml +++ b/man/sd_bus_negotiate_fds.xml @@ -152,7 +152,7 @@ <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_start</refentrytitle><manvolnum>3</manvolnum></citerefentry>, - <citerefentry><refentrytitle>sd_bus_message_can_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>, + <citerefentry><refentrytitle>sd_bus_can_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_message_get_monotonic_usec</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_message_get_realtime_usec</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd_bus_message_get_seqnum</refentrytitle><manvolnum>3</manvolnum></citerefentry>, diff --git a/man/sd_bus_reply_method_error.xml b/man/sd_bus_reply_method_error.xml index 0a85557ec6..dcf9ee299f 100644 --- a/man/sd_bus_reply_method_error.xml +++ b/man/sd_bus_reply_method_error.xml @@ -84,7 +84,7 @@ <para>The <function>sd_bus_reply_method_error()</function> function sends an error reply to the <parameter>call</parameter> message. The error structure <parameter>e</parameter> specifies the error to send, and is used as described in - <citerefentry><refentrytitle>sd_bus_message_new_error</refentrytitle><manvolnum>3</manvolnum></citerefentry>. + <citerefentry><refentrytitle>sd_bus_message_new_method_error</refentrytitle><manvolnum>3</manvolnum></citerefentry>. If no reply is expected to <parameter>call</parameter>, this function succeeds without sending a reply.</para> diff --git a/man/sd_bus_set_watch_bind.xml b/man/sd_bus_set_watch_bind.xml index 0c21050390..9625652d2a 100644 --- a/man/sd_bus_set_watch_bind.xml +++ b/man/sd_bus_set_watch_bind.xml @@ -64,8 +64,8 @@ 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 <citerefentry><refentrytitle>sd_bus_send</refentrytitle><manvolnum>3</manvolnum></citerefentry>, - <citerefentry><refentrytitle>sd_bus_add_match_async</refentrytitle><manvolnum>3</manvolnum></citerefentry> or - <citerefentry><refentrytitle>sd_bus_request_match_async</refentrytitle><manvolnum>3</manvolnum></citerefentry>) do + <citerefentry><refentrytitle>sd_bus_call_async</refentrytitle><manvolnum>3</manvolnum></citerefentry>, + <citerefentry><refentrytitle>sd_bus_add_match_async</refentrytitle><manvolnum>3</manvolnum></citerefentry>) do not block in this case, and safely enqueue the requested operations to be dispatched the instant the connection is set up.</para> diff --git a/man/sd_hwdb_get.xml b/man/sd_hwdb_get.xml index ded8721537..1372f4d80c 100644 --- a/man/sd_hwdb_get.xml +++ b/man/sd_hwdb_get.xml @@ -148,7 +148,7 @@ <para> <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, - <citerefentry><refentrytitle>systemd-udev.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>, + <citerefentry><refentrytitle>systemd-udevd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd-hwdb</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd-hwdb</refentrytitle><manvolnum>8</manvolnum></citerefentry> </para> diff --git a/man/sd_hwdb_new.xml b/man/sd_hwdb_new.xml index 257b347b9b..8f1c01b731 100644 --- a/man/sd_hwdb_new.xml +++ b/man/sd_hwdb_new.xml @@ -112,7 +112,7 @@ <para> <citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>, - <citerefentry><refentrytitle>systemd-udev.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>, + <citerefentry><refentrytitle>systemd-udevd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>, <citerefentry><refentrytitle>sd-hwdb</refentrytitle><manvolnum>3</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd-hwdb</refentrytitle><manvolnum>3</manvolnum></citerefentry> </para> diff --git a/man/systemd-machined.service.xml b/man/systemd-machined.service.xml index ab58d8fd3f..5172f6511a 100644 --- a/man/systemd-machined.service.xml +++ b/man/systemd-machined.service.xml @@ -76,7 +76,7 @@ <listitem><para>The <citerefentry><refentrytitle>sd-bus</refentrytitle><manvolnum>3</manvolnum></citerefentry> library exposes the - <citerefentry><refentrytitle>sd_bus_open_system_container</refentrytitle><manvolnum>3</manvolnum></citerefentry> + <citerefentry><refentrytitle>sd_bus_open_system_machine</refentrytitle><manvolnum>3</manvolnum></citerefentry> call to connect to the system bus of any registered container.</para></listitem> <listitem><para>The diff --git a/man/systemd-networkd.service.xml b/man/systemd-networkd.service.xml index 94a7bfd5ef..2913bb953d 100644 --- a/man/systemd-networkd.service.xml +++ b/man/systemd-networkd.service.xml @@ -92,7 +92,7 @@ <citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>, <citerefentry><refentrytitle>systemd-networkd-wait-online.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>, - <citerefentry><refentrytitle>systemd-networkd-generator.service</refentrytitle><manvolnum>8</manvolnum></citerefentry> + <citerefentry><refentrytitle>systemd-network-generator.service</refentrytitle><manvolnum>8</manvolnum></citerefentry> </para> </refsect1> diff --git a/man/systemd.link.xml b/man/systemd.link.xml index 7e17bf095f..d7724a0a59 100644 --- a/man/systemd.link.xml +++ b/man/systemd.link.xml @@ -27,7 +27,7 @@ <title>Description</title> <para>A plain ini-style text file that encodes configuration for matching network devices, used by - <citerefentry><refentrytitle>systemd-udev</refentrytitle><manvolnum>8</manvolnum></citerefentry> and in + <citerefentry><refentrytitle>systemd-udevd</refentrytitle><manvolnum>8</manvolnum></citerefentry> and in particular its <command>net_setup_link</command> builtin. See <citerefentry><refentrytitle>systemd.syntax</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a general description of the syntax.</para> diff --git a/man/systemd.service.xml b/man/systemd.service.xml index a4a49f39af..61484d530c 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -1078,8 +1078,8 @@ manager. If set to <constant>kill</constant> 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 <varname>DefaultOOMPolicy=</varname> in - <citerefentry><refentrytitle>system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> is - set to, except for services where <varname>Delegate=</varname> is turned on, where it defaults to + <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry> + is set to, except for services where <varname>Delegate=</varname> is turned on, where it defaults to <constant>continue</constant>.</para> <para>Use the <varname>OOMScoreAdjust=</varname> setting to configure whether processes of the unit |