Hey,
this is an easy one. You could have found the answer with man bash
(but who the heck wants to read the whole thing!!!).
I will first give you the little recipe, then explains what it
does (in case you don't care).
some_command 2> some_path_to_a_file
Bash (and like most shells) uses 2 streams. stdout and stderr.
stdout is 1 and stderr is 2. You can create more streams if you like, but,
I am not sure how, since I do not use (and do not understand what I
would do with) more than these streams anyway.
You can also redirect a stream to the other one like this
some_comand 2>&1 >/dev/null
This will make any command truely shut up. It is important to note
that if you use pipes, only stdout is redirected, and if you redirect
stderr at the end of the pipe, if the first command gives an error, it
will be printed on the screen.
For more info, try man bash (and search quickly into it with /).
Papi
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
