diff options
author | Yu Watanabe <watanabe.yu+github@gmail.com> | 2022-12-14 06:29:25 +0100 |
---|---|---|
committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2022-12-14 16:07:17 +0100 |
commit | f0d8358c245b4d0012d8db52dbf42bdebbe1b2bc (patch) | |
tree | e0bb91c04a72ff3b60c78265815886961fbae6af /man/sd_id128_get_machine.xml | |
parent | sd-id128: also refuse an empty invocation ID (diff) | |
download | systemd-f0d8358c245b4d0012d8db52dbf42bdebbe1b2bc.tar.xz systemd-f0d8358c245b4d0012d8db52dbf42bdebbe1b2bc.zip |
man: update documents for sd_id128_get_invocation()
Diffstat (limited to 'man/sd_id128_get_machine.xml')
-rw-r--r-- | man/sd_id128_get_machine.xml | 18 |
1 files 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 |