stderr is filehandle 2. To redirect it to a file use 2> on the command line:
$ command <filein >fileout 2>errout McKown, John wrote:
I know this forum is mainly for support type questions. I.e. "how to". Does anybody know of a good, relatively polite, forum for asking questions about software development on and for Linux? Having said the above, the following is an example of the type of question that I have in mind. One of the conventions that we use is to use the dash mark by itself to stand for "stdin" or "stdout", depending on whether we are expecting an input or output file name. Is there a convention for using "stderr" in place of an output file name? Or is it not expected to want to direct "file type" output to stderr? Thanks for any pointers. Yes, I'm writing some software, in Java, that I plan to run on Linux. I will likely use the GNU approach to parameters, prefix with -- and use descriptive names, rather than the older UNIX convention of a single dash and single letter. E.g --version instead of -v. This is to avoid questions such as does -v mean --version or --verbose? John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell [email protected] * www.HealthMarkets.com
-- Rich Smrcina ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
