08-20-2002
'tee' STDERR output (ksh)
Hi everyone,
KSH question: I know you can 'tee' STDOUT to have the output go to multiple targets; can you do the same with STDERR?
For example:
ls |tee /tmp/file.txt
Will redirect STDOUT to both the screen and the '/tmp/file.txt' file. Is there a way of doing the same thing for STDERR? Ultimately what I'd like is to send STDOUT to the screen and STDERR to both the screen and a debug file.
Thank in advance for any help you can provide.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I write a sh script that zip and copy to tape all files that older then 2 hours.
1. The way I choose is - touch a file with "now - 2 hours", then use fine with '! -newer'
2. Do you have any other idea to do it ?
tnx. (1 Reply)
Discussion started by: yairon
1 Replies
2. Programming
I need to compile a file,but 'make' does
not work.please tell me how to use it or
need which tools? (3 Replies)
Discussion started by: dsun5
3 Replies
3. Shell Programming and Scripting
I wonder how I shall read the result below, especially 'what'
shown below.
The result was shown when I entered 'w'.
E.g what is TOP? What is gosh ( what does selmgr mean?)?
login@ idle JCPU PCPU what
6:15am 7:04 39 39 TOP
6:34am 6:45 45 45 TOP
6:41am ... (1 Reply)
Discussion started by: Aelgen
1 Replies
4. UNIX for Dummies Questions & Answers
I asked a similar question earlier and got a very good answer but a new doubt came up. This is a few lines of a '/sbin/ifconfig' command on my PC:
RX packets:3781025 errors:0 dropped:0 overruns:0 frame:0
TX packets:1941909 errors:0 dropped:0 overruns:0 carrier:0
Does the RX and TX packets... (1 Reply)
Discussion started by: mint1981
1 Replies
5. Filesystems, Disks and Memory
Hi, guys, I have a big problem.
I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It soon becomes a large file.
I wander if there are some mistakes configuring the workstation.
the /var/adm/message is as follow:
... (1 Reply)
Discussion started by: cloudsmell
1 Replies
6. UNIX for Dummies Questions & Answers
Hi, guys, I have a big problem.
I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It becomes a large file in a short time.
I wander if there are some mistakes configuring the workstation.
the /var/adm/message is as follow:
... (3 Replies)
Discussion started by: cloudsmell
3 Replies
7. UNIX for Dummies Questions & Answers
echo 'it's friday'
why appear the > (3 Replies)
Discussion started by: yls177
3 Replies
8. Email Antispam Techniques and Email Filtering
Here is a crude procmail recipe that I quickly created (NOT a procmail recipe expert, btw) that has been catching lots of spam (current second after the charset_spam recipe posted earlier):
:0B
* .*If.you.do.not.wish.to.receive...*
more_spam
:0B
* You.requested.to.receive.this.mailing... (0 Replies)
Discussion started by: Neo
0 Replies
9. UNIX for Advanced & Expert Users
Somehow someone created a file named '-ov' in the root directory.
Given the name, the how was probably the result of some cpio command they bozo'ed.
I've tried a number of different ways to get rid of it using * and ? wildcards, '\' escape patterns etc.. They all fail with " illegal option --... (3 Replies)
Discussion started by: GSalisbury
3 Replies
10. Shell Programming and Scripting
Hopefully this doesn't come off as too much of a "newbie" question or a flamebait. But I have recently begun working with a Sun Solaris box after having spent the past five years working with RedHat. From what i can tell, thing look fairly similar and the 'man' command is some help. But I've... (7 Replies)
Discussion started by: deckard
7 Replies
LEARN ABOUT DEBIAN
systemd-cat
SYSTEMD-CAT(1) systemd-cat SYSTEMD-CAT(1)
NAME
systemd-cat - Connect a pipeline or program's output with the journal
SYNOPSIS
systemd-cat [OPTIONS...] [COMMAND] [ARGUMENTS...]
systemd-cat [OPTIONS...]
DESCRIPTION
systemd-cat may be used to connect STDOUT and STDERR of a process with the journal, or as a filter tool in a shell pipeline to pass the
output the previous pipeline element generates to the journal.
If no parameter is passed systemd-command will write everything it reads from standard input (STDIN) to the journal.
If parameters are passed they are executed as command line with standard output (STDOUT) and standard error output (STDERR) connected to
the journal, so that all it writes is stored in the journal.
OPTIONS
The following options are understood:
--h, --help
Prints a short help text and exits.
--version
Prints a short version string and exits.
-t, --identifier=
Specify a short string that is used to identify the logging tool. If not specified no identifying string is written to the journal.
-p, --priority=
Specify the default priority level for the logged messages. Pass one of emerg, alert, crit, err, warning, notice, info, debug, resp. a
value between 0 and 7 (corresponding to the same named levels). These priority values are the same as defined by syslog(3). Defaults to
info. Note that this simply controls the default, individual lines may be logged with different levels if they are prefixed
accordingly. For details see --level-prefix= below.
--level-prefix=
Controls whether lines read are parsed for syslog priority level prefixes. If enabled (the default) a line prefixed with a priority
prefix such as <5> is logged at priority 5 (notice), and similar for the other priority levels. Takes a boolean argument.
EXIT STATUS
On success 0 is returned, a non-zero failure code otherwise.
EXAMPLES
Example 1. Invoke a program
This calls /bin/ls with STDOUT/STDERR connected to the journal:
# systemd-cat ls
Example 2. Usage in a shell pipeline
This builds a shell pipeline also invoking /bin/ls and writes the output it generates to the journal:
# ls | systemd-cat
Even though the two examples have very similar effects the first is preferable since only one process is running at a time, and both STDOUT
and STDERR are captured while in the second example only STDOUT is captured.
SEE ALSO
systemd(1), systemctl(1), logger(1)
AUTHOR
Lennart Poettering <lennart@poettering.net>
Developer
systemd 10/07/2013 SYSTEMD-CAT(1)