I'm watching the output of my complicated command with less, problem is the stderr gets lost. stderr lines normally get listed inbetween stdout lines inside less. I would like them to be printed to the console, and when I exit less, to see them there together.
I realize there might be no solution to this, I read about tee and multitee but no luck so far.
You have to redirect stderr to stdout:
$ ./somecommad 2>&1 | less
Check the manual for you shell (e.g. man bash.)
Maybe
command 2> command.err | less; cat command.err; rm command.err
Addendum
Here follows a clarification for folk who neglect to carefully read the question and who didn't read the OP's clarifying comment above.
haelix pointed out:
stderr lines normally get listed inbetween stdout lines inside less
and, in a comment for early answerers, wrote:
You're telling me how to redirect stderr to stdout but that's not what I wanted. I don't want stderr to mix with stdout inside less. I would like stderr to be in the terminal when I exit less
The problem is probably platform specific, it is certainly something I have experienced on older Unix SVR4 platforms.
If, on such platforms, you do something like
find / ... | less
any error messages (e.g. directory permissions) appear like this in less
stdout line 1
stdout line 2
error message text
stdout line 4
so that output lines are obscured by error messages.
If you refresh the page the output lines are shown correctly but you lose the error messages. When you exit less the screen is cleared except for a command prompt.
If you do something like
find / ... 2>&1 | less
The error messages are intermingled with the standard output. Again when you exit less, the screen is empty.
If you want to first peruse only the standard output in less, then see the error messages after exiting less, you need a different solution.
That is what I was tentatively suggesting in my original, two-line answer.
One thing that was lacking from all the answers so far is the reason, why this is happening. The problem here is some kind of race-condition between the process outputting stuff to stderr and less displaying output from stdout on the terminal. If less starts displaying after all output to stderr has been printed to the terminal, then less will preserve that and you can see the messages after exiting less. OTOH if less has already started displaying stuff, then error messages intermingle with less's output and nothing is preserved after less exits (because less just preserves the terminal as it was before it started and doesn't know anything about the error messages that came in between).
You can see that easily, if you do e.g.
grep foo -r /etc | less
All the "Permission denied" error messages mix up with less output and nothing will be there after you exit. If you do
grep foo -r /etc | (sleep 10; less)
all (or at least most) of the error messages have been printed to the terminal before less gets a chance to display output and you will see the error messages afterwards.
Of course, you don't usually want to wait 10 seconds before you start less, but with Linux you can also supply fractional values for the waiting time, and with fast running processes often something as little as sleep 0.1 is enough to avoid the race condition. (But, of course, if you want or have to be on the really safe side use RedGrittyBrick's solution).
You need to understand the concept of "file descriptors". Usually, a unix application will start with three special file descriptors:
The "pipe" | in the shell connects stdout from one process with stdin of the next.
Errors are - by design - not fed to stdin of the next process. They will often not make sense to the next application, and should not be hidden from the user.
If you want to mix the errors into stdout, you can use e.g. 2>&1, which says essentially "append stderr to stdout". For example
find /etc 2>&1 | less
should also include error output from inaccessible files.
find /etc 2>&1 >/dev/null | less
will give you the errors only.
I'm confused about your question, as far as I ca tell your desired behavior is the default.
When I use
#include <stdio.h>
int main(int argc, char**argv){
for (int j=0; j<10; ++j){
fprintf( (j%2 ? stdout : stderr) , "%d\n" , j);
}
return 0;
}
to get a simple test,
$ ./testredirection | less
does just what you ask. That is I see
1
3
5
7
9
(END)
in less and
$ ./testredirection | less
0
2
4
6
8
$
when I quit less
I happen to encounter this problem in one of my Debian 5.0's recently. for example, ls abc | less I find that the error message go into less, which against my knowledge.
After some attempts, I found that it is just something related to screen buffers. stderr does NOT go into less actually. You can use Up or Down arrow keys (or j/k) to demonstrate.
