Something like this will work for bash
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.
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)
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT PLAN9
rewrite
REWRITE(6) Games Manual REWRITE(6)NAME
rewrite - mail rewrite rules
SYNOPSIS
/mail/lib/rewrite
DESCRIPTION Mail(1) uses rewrite rules to convert mail destinations into commands used to dispose of the mail. Each line of the file is a rule. Blank
lines and lines beginning with # are ignored.
Each rewriting rule consists of (up to) 4 strings:
pattern
A regular expression in the style of regexp(6). The pattern is applied to mail destination addresses. The pattern match is case-
insensitive and must match the entire address.
type The type of rule; see below.
arg1 An ed(1) style replacement string, with
standing for the text matched by the nth parenthesized subpattern.
arg2 Another ed(1) style replacement string.
In each of these fields the substring s is replaced by the login id of the sender and the substring l is replaced by the name of the
local machine.
When delivering a message, mail starts with the first rule and continues down the list until a pattern matches the destination address. It
then performs one of the following actions depending on the type of the rule:
>> Append the mail to the file indicated by expanding arg1, provided that file appears to be a valid mailbox.
| Pipe the mail through the command formed from concatenating the expanded arg1 and arg2.
alias Replace the address by the address(es) specified by expanding arg1 and recur.
translate
Replace the address by the address(es) output by the command formed by expanding arg1 and recur.
Mail expands the addresses recursively until each address has matched a >> or | rule or until the recursion depth indicates a rewriting
loop (currently 32).
If mail(1) is called with more than one address and several addresses match | rules and result in the same expanded arg1, the message is
delivered to all those addresses by a single command, composed by concatenating the common expanded arg1 and each expanded arg2. This mail
bundling is performed to reduce the number of times the same message is transmitted across a network. For example, with the following re-
write rule
([^!]*.att.com)!(.*) | "/mail/lib/qmail 's' 'net!1'" "'2'"
if user presotto runs the command
% mail research.att.com!ken research.att.com!rob
there will follow only one execution of the command
/mail/lib/qmail presotto net!research.att.com ken rob
Here /mail/lib/qmail is an rc(1) script used for locally queuing remote mail.
In the event of an error, the disposition of the mail depends on the name of the command executing the rewrite. If the command is called
mail and is run by $user, the command will print an error and deposit the message in /mail/box/$user/dead.letter. If the command is called
rmail, usually because it was invoked to deliver mail arriving over the network, the message will be returned to the sender. The returned
message will appear to have been sent by user postmaster.
SEE ALSO mail(1)REWRITE(6)