42 lines
2.1 KiB
Diff
42 lines
2.1 KiB
Diff
|
From 6715fc716fc843c3877160a8220af935c159e789 Mon Sep 17 00:00:00 2001
|
||
|
|
From: Yu Watanabe <watanabe.yu+github@gmail.com>
|
||
|
|
Date: Wed, 14 Dec 2022 14:29:25 +0900
|
||
|
|
Subject: [PATCH] man: update documents for sd_id128_get_invocation()
|
||
|
|
|
||
|
|
(cherry picked from commit f0d8358c245b4d0012d8db52dbf42bdebbe1b2bc)
|
||
|
|
|
||
|
|
Related: RHEL-27512
|
||
|
|
---
|
||
|
|
man/sd_id128_get_machine.xml | 18 ++++++++++++++----
|
||
|
|
1 file changed, 14 insertions(+), 4 deletions(-)
|
||
|
|
|
||
|
|
diff --git a/man/sd_id128_get_machine.xml b/man/sd_id128_get_machine.xml
|
||
|
|
index 075caffb2b..cdab87ab63 100644
|
||
|
|
--- a/man/sd_id128_get_machine.xml
|
||
|
|
+++ b/man/sd_id128_get_machine.xml
|
||
|
|
@@ -94,10 +94,20 @@
|
||
|
|
has properties similar to the machine ID during that time.</para>
|
||
|
|
|
||
|
|
<para><function>sd_id128_get_invocation()</function> returns the invocation ID of the currently executed
|
||
|
|
- service. In its current implementation, this reads and parses the <varname>$INVOCATION_ID</varname> environment
|
||
|
|
- variable that the service manager sets when activating a service, see
|
||
|
|
- <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry> for details. The
|
||
|
|
- ID is cached internally. In future a different mechanism to determine the invocation ID may be added.</para>
|
||
|
|
+ service. In its current implementation, this tries to read and parse the following:
|
||
|
|
+ <itemizedlist>
|
||
|
|
+ <listitem>
|
||
|
|
+ <para>The <varname>$INVOCATION_ID</varname> environment variable that the service manager sets when
|
||
|
|
+ activating a service.</para>
|
||
|
|
+ </listitem>
|
||
|
|
+ <listitem>
|
||
|
|
+ <para>An entry in the kernel keyring that the system service manager sets when activating a service.
|
||
|
|
+ </para>
|
||
|
|
+ </listitem>
|
||
|
|
+ </itemizedlist>
|
||
|
|
+ See <citerefentry><refentrytitle>systemd.exec</refentrytitle><manvolnum>5</manvolnum></citerefentry>
|
||
|
|
+ for details. The ID is cached internally. In future a different mechanism to determine the invocation ID
|
||
|
|
+ may be added.</para>
|
||
|
|
|
||
|
|
<para>Note that <function>sd_id128_get_machine_app_specific()</function>,
|
||
|
|
<function>sd_id128_get_boot()</function>, <function>sd_id128_get_boot_app_specific()</function>, and
|