daandemeyer / rpms / systemd

Forked from rpms/systemd 2 years ago
Clone
b8c242
From f29b7bcd85d4e8d824d36fecc130a0d74af718f8 Mon Sep 17 00:00:00 2001
b8c242
From: David Tardon <dtardon@redhat.com>
b8c242
Date: Tue, 12 Oct 2021 16:47:48 +0200
b8c242
Subject: [PATCH] Remove unintended additions to systemd-analyze man page
b8c242
b8c242
These changes were introduced in commit
b8c242
a2e00522971897909db2a81b4daf10e5700f453e .
b8c242
b8c242
Resolves: #2004765
b8c242
---
b8c242
 man/systemd-analyze.xml | 51 +----------------------------------------
b8c242
 1 file changed, 1 insertion(+), 50 deletions(-)
b8c242
b8c242
diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
b8c242
index 7c873cbdd1..e17ff0cf90 100644
b8c242
--- a/man/systemd-analyze.xml
b8c242
+++ b/man/systemd-analyze.xml
b8c242
@@ -354,56 +354,7 @@ $ eog targets.svg</programlisting>
b8c242
       they elapse next. This takes the same input as the <varname>OnCalendar=</varname> setting in
b8c242
       <citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
b8c242
       following the syntax described in
b8c242
-      <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>. By
b8c242
-      default, only the next time the calendar expression will elapse is shown; use
b8c242
-      <option>--iterations=</option> to show the specified number of next times the expression
b8c242
-      elapses.</para>
b8c242
-
b8c242
-      <example>
b8c242
-        <title>Show leap days in the near future</title>
b8c242
-
b8c242
-        <programlisting>$ systemd-analyze calendar --iterations=5 '*-2-29 0:0:0'
b8c242
-  Original form: *-2-29 0:0:0
b8c242
-Normalized form: *-02-29 00:00:00
b8c242
-    Next elapse: Sat 2020-02-29 00:00:00 UTC
b8c242
-       From now: 11 months 15 days left
b8c242
-       Iter. #2: Thu 2024-02-29 00:00:00 UTC
b8c242
-       From now: 4 years 11 months left
b8c242
-       Iter. #3: Tue 2028-02-29 00:00:00 UTC
b8c242
-       From now: 8 years 11 months left
b8c242
-       Iter. #4: Sun 2032-02-29 00:00:00 UTC
b8c242
-       From now: 12 years 11 months left
b8c242
-       Iter. #5: Fri 2036-02-29 00:00:00 UTC
b8c242
-       From now: 16 years 11 months left
b8c242
-</programlisting>
b8c242
-      </example>
b8c242
-    </refsect2>
b8c242
-
b8c242
-    <refsect2>
b8c242
-      <title><command>systemd-analyze timespan <replaceable>EXPRESSION</replaceable>...</command></title>
b8c242
-
b8c242
-      <para>This command parses a time span and outputs the normalized form and the equivalent value in
b8c242
-      microseconds. The time span should adhere to the same syntax documented in
b8c242
-      <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
b8c242
-      Values without associated magnitudes are parsed as seconds.</para>
b8c242
-
b8c242
-      <example>
b8c242
-        <title>Show parsing of timespans</title>
b8c242
-
b8c242
-        <programlisting>$ systemd-analyze timespan 1s 300s '1year 0.000001s'
b8c242
-Original: 1s
b8c242
-      μs: 1000000
b8c242
-   Human: 1s
b8c242
-
b8c242
-Original: 300s
b8c242
-      μs: 300000000
b8c242
-   Human: 5min
b8c242
-
b8c242
-Original: 1year 0.000001s
b8c242
-      μs: 31557600000001
b8c242
-   Human: 1y 1us
b8c242
-</programlisting>
b8c242
-      </example>
b8c242
+      <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
b8c242
     </refsect2>
b8c242
 
b8c242
     <refsect2>