Redirect STDOUT & STDERR to file and then on screen Post: 303023891

Login or Register to Ask a Question and Join Our Community

Sponsored Content

Top Forums Shell Programming and Scripting Redirect STDOUT & STDERR to file and then on screen Post 303023891 by RudiC on Tuesday 25th of September 2018 08:41:33 AM

Old

09-25-2018

Registered User

Do you really want to capture ALL remaining session? Above execs aren't necessarily the killall tool for what you need. Howsoever, did you consider teeing output to /dev/tty?

RudiC

View Public Profile for RudiC

Find all posts by RudiC

10 More Discussions You Might Find Interesting

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

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

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

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

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

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

7. Shell Programming and Scripting

redirect stdout and stderr to file wrong order problem with subshell

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

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

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

10. Shell Programming and Scripting

Redirecting STDERR to file and screen, STDOUT only to file

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

LEARN ABOUT REDHAT

killall

KILLALL(1)							   User Commands							KILLALL(1)

NAME

       killall - kill processes by name

SYNOPSIS

       killall [-e,--exact] [-g,--process-group] [-i,--interactive] [-q,--quiet] [-v,--verbose] [-w,--wait] [-V,--version] [-S,--sid] [-c,--con-
       text] [-s,--signal signal] [--] name ...
       killall -l
       killall -V,--version

DESCRIPTION

       killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent.

       Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1).

       If the command name contains a slash (/), processes executing that particular file will be selected for killing, independent of their name.

       killall returns a zero return code if at least one process has been killed for each ilisted command. killall returns zero otherwise.

       A killall process never kills itself (but may kill other killall processes).

OPTIONS

       -e, --exact
	      Require an exact match for very long names. If a command name is longer than 15 characters, the full name may be	unavailable  (i.e.
	      it  is  swapped  out). In this case, killall will kill everything that matches within the first 15 characters. With -e, such entries
	      are skipped.  killall prints a message for each skipped entry if -v is specified in addition to -e,

       -g, --process-group
	      Kill the process group to which the process belongs. The kill signal is only sent once per group, even if multiple processes belong-
	      ing to the same process group were found.

       -i, --interactive
	      Interactively ask for confirmation before killing.

       -l, --list
	      List all known signal names.

       -q, --quiet
	      Do not complain if no processes were killed.

       -v, --verbose
	      Report if the signal was successfully sent.

       -V, --version
	      Display version information.

       -w, --wait
	      Wait  for all killed processes to die. killall checks once per second if any of the killed processes still exist and only returns if
	      none are left.  Note that killall may wait forever if the signal was ignored, had no effect, or  if  the	process  stays	in  zombie
	      state.

       -S     (Flask  only) Specify SID: kill only processes with given SID. Mutually exclusive with -c argument.  Must precede other arguments on
	      command line.

       -c     (Flask only) Specify security context: kill only processes with given security context.  Mutually exclusive with -s.   Must  precede
	      other arguments on the command line.

FILES

       /proc	 location of the proc file system

KNOWN BUGS

       Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way.

       Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user.

       killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans.

AUTHORS

       Werner  Almesberger  <Werner.Almesberger@epfl.ch>  wrote  the original version of psmisc.  Since version 20 Craig Small <csmall@small.drop-
       bear.id.au> can be blamed.

SEE ALSO

       kill(1), fuser(1), pgrep(1), pidof(1), ps(1), kill(2)

Linux								  March 25, 2001							KILLALL(1)