Redirect stdout/stderr, except e.g. "STRING"

10 More Discussions You Might Find Interesting

1. 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...

2. 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

3. Shell Programming and Scripting

tcsh - understanding difference between "echo string" and "echo string > /dev/stdout"

I came across and unexpected behavior with redirections in tcsh. I know, csh is not best for redirections, but I'd like to understand what is happening here. I have following script (called out_to_streams.csh): #!/bin/tcsh -f echo Redirected to STDOUT > /dev/stdout echo Redirected to...

4. Shell Programming and Scripting

how to use "cut" or "awk" or "sed" to remove a string

logs: "/home/abc/public_html/index.php" "/home/abc/public_html/index.php" "/home/xyz/public_html/index.php" "/home/xyz/public_html/index.php" "/home/xyz/public_html/index.php" how to use "cut" or "awk" or "sed" to get the following result: abc abc xyz xyz xyz

5. Red Hat

Redirect STDOUT and STDERR of chsh

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...

6. Shell Programming and Scripting

tar "--totals" writes to stderr not stdout?

I want to use the "--totals" option in GNU tar for some reporting, however I have discovered that it writes the output to stderr not stdout and I would like to know why. This is running from BASH. mkdir /tmp/test touch /tmp/test/foo.file cd /tmp/ tar --totals -clpzf test.tar.gz test 2>...

7. Shell Programming and Scripting

Redirect stdout/stderr to a file globally

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 ...

8. Shell Programming and Scripting

How to redirect stderr and stdout to a file

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...

9. UNIX for Dummies Questions & Answers

redirect stderr and/or stdout to /dev/null from command line

Is it possible to redirect errors at the command line when you run the script such as bash scriptname & 2>/dev/null?

10. Shell Programming and Scripting

Redirect stdout and stderr

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

LEARN ABOUT NETBSD

nohup

NOHUP(1)						    BSD General Commands Manual 						  NOHUP(1)

NAME

     nohup -- invoke a command immune to hangups

SYNOPSIS

     nohup utility [arg ...]

DESCRIPTION

     The nohup command allows the specified utility to be protected from termination if the user should become logged out (for example, due to a
     modem line or TCP/IP connection being dropped).  To do this, nohup sets the SIGHUP signal(3) (``terminal line hangup'') to be ignored, then
     executes utility along with any arguments.

     If the standard output is a terminal, the standard output is appended to the file nohup.out in the current directory.  If standard error is a
     terminal, it is directed to the same place as the standard output.  If the output file nohup.out cannot be created in the current directory,
     nohup attempts to create the file in the user's home directory.  If the file nohup.out cannot be created, either in the current directory or
     the user's home directory, nohup will exit without invoking utility, with an exit value as described below.

ENVIRONMENT

     The following variable is used by nohup.

     HOME  User's home directory.

EXIT STATUS

     The nohup utility exits with one of the following values:

     126     The utility was found but could not be invoked.

     127     The utility could not be found or an error occurred in nohup.

     Otherwise, the exit status of nohup will be that of utility.

SEE ALSO

     signal(3)

STANDARDS

     The nohup command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.

BSD
								   July 15, 2005							       BSD

Shell Programming and Scripting