summaryrefslogtreecommitdiffstats
path: root/man
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2024-12-19 15:32:55 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2024-12-19 15:38:56 +0100
commit06a73d1fb6a8be3f48e727751641d89a5076574f (patch)
tree8547acceb5a7061a220bfcb20266298ba512c026 /man
parentdocs/package-notes: extend description to support PE/COFF files (diff)
downloadsystemd-06a73d1fb6a8be3f48e727751641d89a5076574f.tar.xz
systemd-06a73d1fb6a8be3f48e727751641d89a5076574f.zip
man: update package metadata link and details
The variable names are actually "name" and "version". Not sure why the man page had something different.
Diffstat (limited to 'man')
-rw-r--r--man/systemd-analyze.xml5
-rw-r--r--man/systemd-coredump.xml14
2 files changed, 11 insertions, 8 deletions
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
index 68d006a1ce..019901d00c 100644
--- a/man/systemd-analyze.xml
+++ b/man/systemd-analyze.xml
@@ -862,8 +862,9 @@ alias.service:7: Unknown key name 'MysteryKey' in section 'Service', ignoring.
<para>This command will load the specified files, and if they are ELF objects (executables,
libraries, core files, etc.) it will parse the embedded packaging metadata, if any, and print
- it in a table or json format. See the <ulink url="https://systemd.io/COREDUMP_PACKAGE_METADATA/">
- Packaging Metadata</ulink> documentation for more information.</para>
+ it in a table or json format. See the
+ <ulink url="https://systemd.io/PACKAGE_METADATA_FOR_EXECUTABLE_FILES/">
+ Package Metadata for Executable Files</ulink> document for more information.</para>
<example>
<title>Print information about a core file as JSON</title>
diff --git a/man/systemd-coredump.xml b/man/systemd-coredump.xml
index 737b80de9a..a7862f9c0f 100644
--- a/man/systemd-coredump.xml
+++ b/man/systemd-coredump.xml
@@ -412,12 +412,14 @@ flags: ...
<term><varname>COREDUMP_PACKAGE_VERSION=</varname></term>
<term><varname>COREDUMP_PACKAGE_JSON=</varname></term>
- <listitem><para>If the executable contained .package metadata ELF notes, they will be
- parsed and attached. The <varname>package</varname> and <varname>packageVersion</varname>
- of the 'main' ELF module (ie: the executable) will be appended individually. The
- JSON-formatted content of all modules will be appended as a single JSON object, each with
- the module name as the key. For more information about this metadata format and content, see
- <ulink url="https://systemd.io/COREDUMP_PACKAGE_METADATA/">the coredump metadata spec</ulink>.</para>
+ <listitem><para>If the executable contained .package metadata ELF notes, they will be parsed and
+ attached. The <varname>package</varname> and <varname>version</varname> of the 'main' ELF module
+ (i.e., the executable) will be appended individually. The JSON-formatted content of all modules will
+ be appended as a single JSON object, each with the module name as the key. For more information about
+ this metadata format and content, see the
+ <ulink url="https://systemd.io/PACKAGE_METADATA_FOR_EXECUTABLE_FILES/">Package Metadata for Executable Files</ulink>
+ document.
+ </para>
<xi:include href="version-info.xml" xpointer="v249"/>
</listitem>