log: introduce a macro to format message id

[elogind.git] / man / journalctl.xml

diff --git a/man/journalctl.xml b/man/journalctl.xml
index 651a8a56ad99bc6c9c9ad07ae86f230ebb416579..3786fdf51491f476a4b876adb55272ecbb141bbb 100644 (file)
--- a/man/journalctl.xml
+++ b/man/journalctl.xml
@@ -193,6 +193,7 @@
                                 <literal>export</literal>,
                                 <literal>json</literal>,
                                 <literal>json-pretty</literal>,
                                 <literal>export</literal>,
                                 <literal>json</literal>,
                                 <literal>json-pretty</literal>,

+                                <literal>json-sse</literal>,

                                 <literal>cat</literal>. <literal>short</literal>
                                 is the default and generates an output
                                 that is mostly identical to the
                                 <literal>cat</literal>. <literal>short</literal>
                                 is the default and generates an output
                                 that is mostly identical to the


@@ -219,7 +220,12 @@
                                 structures, but formats them in
                                 multiple lines in order to make them
                                 more readable for
                                 structures, but formats them in
                                 multiple lines in order to make them
                                 more readable for

-                                humans. <literal>cat</literal>
+                                humans. <literal>json-sse</literal>
+                                also formats entries as JSON data
+                                structures, but wraps them in a format
+                                suitable for <ulink
+                                url="https://developer.mozilla.org/en-US/docs/Server-sent_events/Using_server-sent_events">Server-Sent
+                                Events</ulink>. <literal>cat</literal>

                                 generates a very terse output only
                                 showing the actual message of each
                                 journal entry with no meta data, not
                                 generates a very terse output only
                                 showing the actual message of each
                                 journal entry with no meta data, not


@@ -258,11 +264,42 @@
                                 <term><option>--cursor=</option></term>
                                 <term><option>-c</option></term>
 
                                 <term><option>--cursor=</option></term>
                                 <term><option>-c</option></term>
 

-                                <listitem><para>Jump to the location
-                                in the journal specified by the passed
+                                <listitem><para>Start showing entries
+                                from the location in the journal
+                                specified by the passed

                                 cursor.</para></listitem>
                         </varlistentry>
 
                                 cursor.</para></listitem>
                         </varlistentry>
 

+                        <varlistentry>
+                                <term><option>--since=</option></term>
+                                <term><option>--until=</option></term>
+
+                                <listitem><para>Start showing entries
+                                newer or of the specified date,
+                                resp. older or of the specified
+                                date. Date specifications should be of
+                                the format "2012-10-30 18:17:16". If
+                                the time part is omitted, 00:00:00 is
+                                assumed. If only the seconds component
+                                is omitted, :00 is assumed. If the
+                                date component is ommitted, the
+                                current day is assumed. Alternatively
+                                the strings
+                                <literal>yesterday</literal>,
+                                <literal>today</literal>,
+                                <literal>tomorrow</literal> are
+                                understood, which refer to 00:00:00 of
+                                the day before the current day, the
+                                current day, resp the day after the
+                                current day. <literal>now</literal>
+                                refers to the current time. Finally,
+                                relative times may be specified,
+                                prefixed with <literal>-</literal> or
+                                <literal>+</literal>, referring to
+                                times before resp. after the current
+                                time.</para></listitem>
+                        </varlistentry>
+

                         <varlistentry>
                                 <term><option>--directory=</option></term>
                                 <term><option>-D</option></term>
                         <varlistentry>
                                 <term><option>--directory=</option></term>
                                 <term><option>-D</option></term>