]> git.ipfire.org Git - thirdparty/systemd.git/blobdiff - man/systemd-coredump.xml
meson: print warnings if the "nobody" user/group name is not compatible with the...
[thirdparty/systemd.git] / man / systemd-coredump.xml
index 7243467dc2d6a2511d4110d90a72ffaab0763404..1341866463a6d2654425de5320bf26dce78c9cb9 100644 (file)
@@ -3,6 +3,8 @@
         "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 
 <!--
+  SPDX-License-Identifier: LGPL-2.1+
+
   This file is part of systemd.
 
   Copyright 2014 Zbigniew JÄ™drzejewski-Szmek
@@ -91,7 +93,7 @@
     <para>It is also possible to invoke <command>systemd-coredump</command> with
     <option>--backtrace</option> option. In this case, <command>systemd-coredump</command> expects
     a journal entry in the journal
-    <ulink url="http://www.freedesktop.org/wiki/Software/systemd/export">Journal Export Format</ulink>
+    <ulink url="https://www.freedesktop.org/wiki/Software/systemd/export">Journal Export Format</ulink>
     on standard input. The entry should contain a <varname>MESSAGE=</varname> field and any additional
     metadata fields the caller deems reasonable. <command>systemd-coredump</command> will append
     additional metadata fields in the same way it does for core dumps received from the kernel. In
 
     <para>In order to by used in the <option>--backtrace</option> mode, an appropriate backtrace
     handler must be installed on the sender side. For example, in case of
-    <citerefentry><refentrytitle>python</refentrytitle><manvolnum>1</manvolnum></citerefentry>, this
+    <citerefentry project='die-net'><refentrytitle>python</refentrytitle><manvolnum>1</manvolnum></citerefentry>, this
     means a <varname>sys.excepthook</varname> must installed, see
     <ulink url="https://github.com/keszybz/systemd-coredump-python">systemd-coredump-python</ulink>.
     </para>