Home/ Questions/Q 8191127
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-07T03:51:05+00:00

There are plenty of threads here discussing how to do this for scripts or

  • 0

There are plenty of threads here discussing how to do this for scripts or for the cmdline (mostly involving pipes, redirections, tee).
What I didn’t find is a solution which can be set up once and then just works globally, without manipulating single scripts or adding something to every command line.

What I want to achieve is something like described in the top answer of
How do I write stderr to a file while using "tee" with a pipe?

Isn’t it possible to configure the bash session so that all stderr output is logged to a file, while still writing it to console? Something I could add to .bashrc and thus automatically set up every time I login?

Software: Bash 4.2.24(1)-release (x86_64-pc-linux-gnu), xterm, Ubuntu 12.04

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Try this variation on @0xC0000022L’s previous solution (put it in your .bash_profile):

    exec 2> >( tee log.file > /dev/tty )

    A couple of caveats:

    1. The prompt and anything you type at the command line are printed to stderr, and so will be logged in your file.

    2. There could be an issue with the newline that terminates a command not being displayed in your terminal; I observe it on my Linux host, but not on my Mac OS X laptop. Perhaps someone else can explain and/or fix the issue. For example, if I type “echo stdout”, I see the following:

      $ echo stdoutstdout
$
    • 0