2012-03-16 01:19:36 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<!--
This file is part of systemd.
2012-03-16 01:36:33 +04:00
Copyright 2012 Lennart Poettering
2012-03-16 01:19:36 +04:00
systemd is free software; you can redistribute it and/or modify it
2012-04-12 02:20:58 +04:00
under the terms of the GNU Lesser General Public License as published by
the Free Software Foundation; either version 2.1 of the License, or
2012-03-16 01:19:36 +04:00
(at your option) any later version.
systemd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
2012-04-12 02:20:58 +04:00
Lesser General Public License for more details.
2012-03-16 01:19:36 +04:00
2012-04-12 02:20:58 +04:00
You should have received a copy of the GNU Lesser General Public License
2012-03-16 01:19:36 +04:00
along with systemd; If not, see <http: / / w w w . g n u . o r g / l i c e n s e s /> .
-->
<refentry id= "systemd-cat" >
<refentryinfo >
<title > systemd-cat</title>
<productname > systemd</productname>
<authorgroup >
<author >
<contrib > Developer</contrib>
<firstname > Lennart</firstname>
<surname > Poettering</surname>
<email > lennart@poettering.net</email>
</author>
</authorgroup>
</refentryinfo>
<refmeta >
<refentrytitle > systemd-cat</refentrytitle>
<manvolnum > 1</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd-cat</refname>
<refpurpose > Connect a pipeline or program's output with the journal</refpurpose>
</refnamediv>
<refsynopsisdiv >
<cmdsynopsis >
<command > systemd-cat <arg choice= "opt" rep= "repeat" > OPTIONS</arg> <arg > COMMAND</arg> <arg choice= "opt" rep= "repeat" > ARGUMENTS</arg> </command>
</cmdsynopsis>
<cmdsynopsis >
<command > systemd-cat <arg choice= "opt" rep= "repeat" > OPTIONS</arg> </command>
</cmdsynopsis>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > <command > systemd-cat</command> may be used to
2014-02-15 07:00:06 +04:00
connect the standard input and output of a process to the
2012-03-16 01:19:36 +04:00
journal, or as a filter tool in a shell pipeline to
pass the output the previous pipeline element
generates to the journal.</para>
2013-09-12 23:12:49 +04:00
<para > If no parameter is passed,
2012-03-22 03:35:19 +04:00
<command > systemd-cat</command> will write
2014-02-15 07:00:06 +04:00
everything it reads from standard input (stdin) to the journal.</para>
2012-03-16 01:19:36 +04:00
2013-09-12 23:12:49 +04:00
<para > If parameters are passed, they are executed as
2014-02-15 07:00:06 +04:00
command line with standard output (stdout) and standard
error output (stderr) connected to the journal, so
2012-03-16 01:19:36 +04:00
that all it writes is stored in the journal.</para>
</refsect1>
<refsect1 >
<title > Options</title>
<para > The following options are understood:</para>
<variablelist >
<varlistentry >
2012-06-27 12:48:13 +04:00
<term > <option > -h</option> </term>
2012-03-16 01:19:36 +04:00
<term > <option > --help</option> </term>
<listitem > <para > Prints a short help
text and exits.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --version</option> </term>
<listitem > <para > Prints a short version
string and exits.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > -t</option> </term>
<term > <option > --identifier=</option> </term>
<listitem > <para > Specify a short string
that is used to identify the logging
2013-09-12 23:12:49 +04:00
tool. If not specified, no identification
2012-03-16 01:19:36 +04:00
string is written to the journal.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > -p</option> </term>
<term > <option > --priority=</option> </term>
<listitem > <para > Specify the default
priority level for the logged
messages. Pass one of
<literal > emerg</literal> ,
<literal > alert</literal> ,
<literal > crit</literal> ,
<literal > err</literal> ,
<literal > warning</literal> ,
<literal > notice</literal> ,
<literal > info</literal> ,
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
2012-10-15 22:59:12 +04:00
<literal > debug</literal> , or a
2012-03-16 01:19:36 +04:00
value between 0 and 7 (corresponding
to the same named levels). These
priority values are the same as
defined by
<citerefentry > <refentrytitle > syslog</refentrytitle> <manvolnum > 3</manvolnum> </citerefentry> . Defaults
to <literal > info</literal> . Note that
this simply controls the default,
individual lines may be logged with
different levels if they are prefixed
accordingly. For details see
<option > --level-prefix=</option>
below.</para> </listitem>
</varlistentry>
<varlistentry >
<term > <option > --level-prefix=</option> </term>
<listitem > <para > Controls whether lines
read are parsed for syslog priority
level prefixes. If enabled (the
2013-09-12 23:12:49 +04:00
default), a line prefixed with a
2012-03-16 01:19:36 +04:00
priority prefix such as
<literal > < 5> </literal> is logged
at priority 5
(<literal > notice</literal> ), and
similar for the other priority
levels. Takes a boolean
argument.</para> </listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > Exit status</title>
2013-12-26 05:47:44 +04:00
<para > On success, 0 is returned, a non-zero failure
2012-03-16 01:19:36 +04:00
code otherwise.</para>
</refsect1>
<refsect1 >
<title > Examples</title>
<example >
<title > Invoke a program</title>
2013-05-03 08:55:20 +04:00
<para > This calls <filename noindex= 'true' > /bin/ls</filename>
2014-02-15 07:00:06 +04:00
with standard output and error connected to the
2012-03-16 01:19:36 +04:00
journal:</para>
<programlisting > # systemd-cat ls</programlisting>
</example>
<example >
<title > Usage in a shell pipeline</title>
<para > This builds a shell pipeline also
invoking <filename > /bin/ls</filename> and
writes the output it generates to the
journal:</para>
<programlisting > # ls | systemd-cat</programlisting>
</example>
<para > Even though the two examples have very similar
effects the first is preferable since only one process
2014-02-15 07:00:06 +04:00
is running at a time, and both stdout and stderr are
2014-02-17 06:37:13 +04:00
captured while in the second example, only stdout is
2012-03-16 01:19:36 +04:00
captured.</para>
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemctl</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > logger</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry>
</para>
</refsect1>
</refentry>