10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have to redirect STDERR messages both to screen and also capture the same in a file but STDOUT only to the same file.
I have searched in this formum for a solution, but something like
srcipt 3>&1 >&2 2>&3 3>&- | tee errs
doesn't work for me...
Has anyone an idea??? (18 Replies)
Discussion started by: thuranga
18 Replies
2. Shell Programming and Scripting
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
3. Shell Programming and Scripting
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
4. Shell Programming and Scripting
Hello
I read a lot of post related to this topic, but nothing helped me. :mad:
I'm running a ksh script with subshell what processing some ldap command. I need to check output for possible errors.
#!/bin/ksh
...
readinput < $QCHAT_INPUT |&
while read -p line
do
echo $line
... (3 Replies)
Discussion started by: Osim
3 Replies
5. Red Hat
EDIT: Nevermind, figured it out! Forgot to put backslashes in my perl script to not process literals!
Hi everyone. I am trying to have this command pass silently. (no output)
chsh -s /bin/sh news
Currently it outputs.
I've tried....
&> /dev/null
1> /dev/null
2>&1 /dev/null
1>&2... (1 Reply)
Discussion started by: austinharris43
1 Replies
6. Shell Programming and Scripting
Hi
I am not if this is possible: is it possible in bach (or another shell) to redirect GLOBALLY the stdout/stderr channels to a file.
So, if I have a script
script.sh
cmd1
cmd2
cmd3
I want all stdout/stderr goes to a file. I know I can do:
./script.sh 1>file 2>&1
OR
... (2 Replies)
Discussion started by: islegmar
2 Replies
7. Shell Programming and Scripting
Hi friends
I am facing one problem while redirecting the out of the stderr and stdout to a file
let example my problem with a simple example
I have a file (say test.sh)in which i run 2 command in the background
ps -ef &
ls &
and now i am run this file and redirect the output to a file... (8 Replies)
Discussion started by: sushantnirwan
8 Replies
8. Shell Programming and Scripting
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
9. Shell Programming and Scripting
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
10. Shell Programming and Scripting
How can I redirect and append stdout and stderr to a file when using cron? Here is my crontab file:
*/5 * * * * /dir/php /dir/process_fns.php >>& /dir/dump.txt
Cron gives me an 'unexpected character found in line' when trying to add my crontab file.
Regards,
Zach Curtis
POPULUS (8 Replies)
Discussion started by: zcurtis
8 Replies
IO::CaptureOutput(3pm) User Contributed Perl Documentation IO::CaptureOutput(3pm)
NAME
IO::CaptureOutput - capture STDOUT and STDERR from Perl code, subprocesses or XS
VERSION
This documentation describes version 1.1102.
SYNOPSIS
use IO::CaptureOutput qw(capture qxx qxy);
# STDOUT and STDERR separately
capture { noisy_sub(@args) } $stdout, $stderr;
# STDOUT and STDERR together
capture { noisy_sub(@args) } $combined, $combined;
# STDOUT and STDERR from external command
($stdout, $stderr, $success) = qxx( @cmd );
# STDOUT and STDERR together from external command
($combined, $success) = qxy( @cmd );
DESCRIPTION
This module provides routines for capturing STDOUT and STDERR from perl subroutines, forked system calls (e.g. "system()", "fork()") and
from XS or C modules.
FUNCTIONS
The following functions will be exported on demand.
capture()
capture &subroutine, $stdout, $stderr;
Captures everything printed to "STDOUT" and "STDERR" for the duration of &subroutine. $stdout and $stderr are optional scalars that will
contain "STDOUT" and "STDERR" respectively.
"capture()" uses a code prototype so the first argument can be specified directly within brackets if desired.
# shorthand with prototype
capture { print __PACKAGE__ } $stdout, $stderr;
Returns the return value(s) of &subroutine. The sub is called in the same context as "capture()" was called e.g.:
@rv = capture { wantarray } ; # returns true
$rv = capture { wantarray } ; # returns defined, but not true
capture { wantarray }; # void, returns undef
"capture()" is able to capture output from subprocesses and C code, which traditional "tie()" methods of output capture are unable to do.
Note: "capture()" will only capture output that has been written or flushed to the filehandle.
If the two scalar references refer to the same scalar, then "STDERR" will be merged to "STDOUT" before capturing and the scalar will hold
the combined output of both.
capture &subroutine, $combined, $combined;
Normally, "capture()" uses anonymous, temporary files for capturing output. If desired, specific file names may be provided instead as
additional options.
capture &subroutine, $stdout, $stderr, $out_file, $err_file;
Files provided will be clobbered, overwriting any previous data, but will persist after the call to "capture()" for inspection or other
manipulation.
By default, when no references are provided to hold STDOUT or STDERR, output is captured and silently discarded.
# Capture STDOUT, discard STDERR
capture &subroutine, $stdout;
# Discard STDOUT, capture STDERR
capture &subroutine, undef, $stderr;
However, even when using "undef", output can be captured to specific files.
# Capture STDOUT to a specific file, discard STDERR
capture &subroutine, $stdout, undef, $outfile;
# Discard STDOUT, capture STDERR to a specific file
capture &subroutine, undef, $stderr, undef, $err_file;
# Discard both, capture merged output to a specific file
capture &subroutine, undef, undef, $mergedfile;
It is a fatal error to merge STDOUT and STDERR and request separate, specific files for capture.
# ERROR:
capture &subroutine, $stdout, $stdout, $out_file, $err_file;
capture &subroutine, undef, undef, $out_file, $err_file;
If either STDOUT or STDERR should be passed through to the terminal instead of captured, provide a reference to undef -- "undef" --
instead of a capture variable.
# Capture STDOUT, display STDERR
capture &subroutine, $stdout, undef;
# Display STDOUT, capture STDERR
capture &subroutine, undef, $stderr;
capture_exec()
($stdout, $stderr, $success, $exit_code) = capture_exec(@args);
Captures and returns the output from "system(@args)". In scalar context, "capture_exec()" will return what was printed to "STDOUT". In list
context, it returns what was printed to "STDOUT" and "STDERR" as well as a success flag and the exit value.
$stdout = capture_exec('perl', '-e', 'print "hello world"');
($stdout, $stderr, $success, $exit_code) =
capture_exec('perl', '-e', 'warn "Test"');
"capture_exec" passes its arguments to "system()" and on MSWin32 will protect arguments with shell quotes if necessary. This makes it a
handy and slightly more portable alternative to backticks, piped "open()" and "IPC::Open3".
The $success flag returned will be true if the command ran successfully and false if it did not (if the command could not be run or if it
ran and returned a non-zero exit value). On failure, the raw exit value of the "system()" call is available both in the $exit_code
returned and in the $? variable.
($stdout, $stderr, $success, $exit_code) =
capture_exec('perl', '-e', 'warn "Test" and exit 1');
if ( ! $success ) {
print "The exit code was " . ($exit_code >> 8) . "
";
}
See perlvar for more information on interpreting a child process exit code.
capture_exec_combined()
($combined, $success, $exit_code) = capture_exec_combined(
'perl', '-e', 'print "hello
"', 'warn "Test
"
);
This is just like "capture_exec()", except that it merges "STDERR" with "STDOUT" before capturing output.
Note: there is no guarantee that text printed to "STDOUT" and "STDERR" in the subprocess will be appear in order. The actual order will
depend on how IO buffering is handled in the subprocess.
qxx()
This is an alias for "capture_exec()".
qxy()
This is an alias for "capture_exec_combined()".
SEE ALSO
o IPC::Open3
o IO::Capture
o IO::Utils
o IPC::System::Simple
AUTHORS
o Simon Flack <simonflk _AT_ cpan.org> (original author)
o David Golden <dagolden _AT_ cpan.org> (co-maintainer since version 1.04)
COPYRIGHT AND LICENSE
Portions copyright 2004, 2005 Simon Flack. Portions copyright 2007, 2008 David Golden. All rights reserved.
You may distribute under the terms of either the GNU General Public License or the Artistic License, as specified in the Perl README file.
perl v5.10.1 2010-02-15 IO::CaptureOutput(3pm)