Sponsored Content
Full Discussion: combined stdout & stderr
Top Forums UNIX for Advanced & Expert Users combined stdout & stderr Post 58490 by zazzybob on Monday 22nd of November 2004 06:22:09 PM
Old 11-22-2004
Something like this will work for bash
Code:
((./myscript arg1 arg2 | tee stdout) 3>&1 1>&2 2>&3 | tee stderr)

This will create two files, stdout and stderr containing the expected output, plus all output will also appear on screen. Replace ./myscript arg1 arg2 with the actual command you're using.

Cheers
ZB
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

stderr & stdout to a file and the right exit code

Hi all, I need to redirect stdout and stderr to a file in a ksh shell. That's not a problem. But I need also the correct exit code for the executed command. In the example below I redirect correctly the stdout & stderr to a file, but I have the exit code of tee command and not for the mv... (2 Replies)
Discussion started by: up69
2 Replies

2. Shell Programming and Scripting

redirecting STDOUT & STDERR

In bash, I need to send the STDOUT and STDERR from a command to one file, and then just STDERR to another file. Doing one or the other using redirects is easy, but trying to do both at once is a bit tricky. Anyone have any ideas? (9 Replies)
Discussion started by: jshinaman
9 Replies

3. Shell Programming and Scripting

getting stderr & stdout output lively modified

This is about getting all output to stderr and stdout localized. Nothing to do with redirecting output to a file (there already are some interesting threads about that issue on this forum). What I intend to do is capturing all lines of text sent to the screen, compare them with an array of... (2 Replies)
Discussion started by: teo ramirez
2 Replies

4. Shell Programming and Scripting

Redirecting STDERR message to STDOUT & file at same time

Friends I have to redirect STDERR messages both to screen and also capture the same in a file. 2 > &1 | tee file works but it also displays the non error messages to file, while i only need error messages. Can anyone help?? (10 Replies)
Discussion started by: vikashtulsiyan
10 Replies

5. Shell Programming and Scripting

Handling Stdout&StdErr for background jobs.

Hello Friends, sorry, i am not very familiar with Unix programming. Could you please help me on this? We have to start different components from a startup script. each components are started as below in the background in a startprocess function $nohup $file $args >>$logFile 2>&1 & ... (0 Replies)
Discussion started by: alvinbush
0 Replies

6. Solaris

Handling Stdout&StdErr for background jobs.

Hello Friends, sorry, i am not very familiar with Unix programming. Could you please help me on this? We have to start different components from a startup script. each components are started as below in the background in a startprocess function $nohup $file $args >>$logFile 2>&1 & ... (1 Reply)
Discussion started by: alvinbush
1 Replies

7. Shell Programming and Scripting

Prepend TimeStamp to STDERR & STDOUT to a file

Currently I am redirecting STDERR and STDOUT to a log file by doing the following { My KSH script contents } 2>&1 | $DEBUGLOG Problem is the STDERR & STDOUT do not have any date/time associated. I want this to be something that i can embed into a script opposed to an argument I use... (4 Replies)
Discussion started by: nitrobass24
4 Replies

8. Shell Programming and Scripting

Redirect STDOUT & STDERR to file and then on screen

Dear all, redirecting STDOUT & STDERR to file is quite simple, I'm currently using: exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.logBut during script execution I would like the output come back again to screen, how to do that? Thanks Lucas (4 Replies)
Discussion started by: Lord Spectre
4 Replies

9. Shell Programming and Scripting

Lost redirecting stderr & stdout to 3 files - one each plus combined

Hi folks I need/want to redirect output (stdout, stderr) from an exec call to separate files. One for stderr only and two(!) different (!) ones for the combined output of stderr and stdout. After some research and testing i got this so far : (( exec ${command} ${command_parameters} 3>&1... (6 Replies)
Discussion started by: MDominok
6 Replies

10. Shell Programming and Scripting

Redirect STDOUT & STDERR to file and then on screen

Dear all, redirecting STDOUT & STDERR to file is quite simple, I'm currently using: Code: exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.log But during script execution I would like the output come back again to screen, how to do that? Thanks Luc edit by bakunin: please use CODE-tags like the... (6 Replies)
Discussion started by: tmonk1
6 Replies
AFQUERY(3)																AFQUERY(3)

NAME
afQuery, afQueryLong, afQueryDouble, afQueryPointer - query the capabilities of the Audio File Library SYNOPSIS
#include <audiofile.h> AUpvlist afQuery (int querytype, int arg1, int arg2, int arg3, int arg4); long afQueryLong (int querytype, int arg1, int arg2, int arg3, int arg4); double afQueryDouble (int querytype, int arg1, int arg2, int arg3, int arg4); void *afQueryPointer (int querytype, int arg1, int arg2, int arg3, int arg4); PARAMETERS
querytype can be one of the following: o AF_QUERYTYPE_FILEFMT o AF_QUERYTYPE_INST o AF_QUERYTYPE_INSTPARAM o AF_QUERYTYPE_COMPRESSION o AF_QUERYTYPE_COMPRESSIONPARAM o AF_QUERYTYPE_MISC o AF_QUERYTYPE_MARK o AF_QUERYTYPE_LOOP arg1, arg2, arg3, and arg4 are integer selectors whose meaning depends upon querytype. RETURN VALUE
Upon success, afQuery will return a non-null AUpvlist value. Upon failure, afQuery will return null while afQueryLong and afQueryDouble will return -1 and afQueryPointer will return null. Pointers representing character strings are owned by the Audio File Library and must not be freed; all other pointer values must be freed by the caller. DESCRIPTION
For AF_QUERYTYPE_FILEFMT, the following selectors are valid values for arg1: AF_QUERY_LABEL Request a short label string for the format (e.g., "aiff"). AF_QUERY_NAME Request a short name for the format (e.g., "MS RIFF WAVE"). AF_QUERY_DESC Request a descriptive name for the format (e.g., "Audio Interchange File Format"). AF_QUERY_IMPLEMENTED Request a boolean value indicating whether the format is implemented for reading and writing in the Audio File Library. AF_QUERY_ID_COUNT Request the total number of formats implemented. AF_QUERY_IDS Request an integer array of the id token values of all implemented file formats. AF_QUERY_COMPRESSION_TYPES Used with the selector AF_QUERY_VALUE_COUNT in arg2, this will return a long integer containing the number of compression schemes available for use within the format specified in arg3. Used with selector AF_QUERY_VALUES, it returns a pointer to an integer array containing the compression id values of the compression schemes supported by the format specified in arg3. AF_QUERY_SAMPLE_FORMATS Used with the selector AF_QUERY_DEFAULT in arg2, this will return the default sample format for the file format specified in arg3. AF_QUERY_SAMPLE_SIZES Used with selector AF_QUERY_DEFAULT in arg2, this will return the default sample width for the file format specified in arg3. For AF_QUERYTYPE_INST, the following selectors are valid for arg1: AF_QUERY_SUPPORTED Request a boolean value indicating whether the file format in arg2 supports instruments. AF_QUERY_MAX_NUMBER Request an integer value indicating the maximum number of instruments supported by the file format in arg2. For AF_QUERYTYPE_INSTPARAM, the following selectors are valid for arg1: AF_QUERY_SUPPORTED Request a boolean value indicating whether the file format in arg2 supports instrument parameters. AF_QUERY_ID_COUNT Request an integer value indicating the number of instrument parameters supported by the file format in arg2. AF_QUERY_IDS Request an integer array containing the instrument parameter values for the file format in arg2. AF_QUERY_TYPE For the file format in arg2, request the type of the instrument parameter in arg3. AF_QUERY_NAME For the file format in arg2, request the name of the instrument parameter in arg3. AF_QUERY_DEFAULT For the file format in arg2, request the default value of the instrument parameter in arg3. ERRORS
afQuery can produce the following errors: AF_BAD_QUERYTYPE The query type is unsupported. AF_BAD_QUERY The arguments to the query are bad. AUTHOR
Michael Pruett <michael@68k.org> Audio File Library 0.3.6 03/06/2013 AFQUERY(3)
All times are GMT -4. The time now is 09:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy