Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Need output of script on screen and file with correct return status of the called script.
Top Forums Shell Programming and Scripting Need output of script on screen and file with correct return status of the called script. Post 302924968 by Prathmesh on Thursday 13th of November 2014 09:04:07 AM
Old 11-13-2014
Quote:
Originally Posted by sea
That case is about the same:
Code:
sh 2.sh
RET=$?

Or likewise:
Code:
sh 2.sh
RET2=$?

sh 3.sh
RET3=$?

or even:
Code:
for script in 2.sh 3.sh;do
    sh $script
    RET=$?
    echo "$script returned: $RET" | tee -a $script.log
    echo "$script returned: $RET" | tee -a allscripts.log
done


Not unless you export the variable, in which case, they must not have the same name, or you can just fetch the latest 'output/export'.
However, you could read the logfile for sure.

hth
I want to catch the output of the $script in log file (both stdout and stderr). How can I do that?

If I use tee command to capture both stdout and stderr like below, I loose the exit status.
Code:
sh $script 2>&1 | tee -a $script.log

Last edited by Prathmesh; 11-13-2014 at 10:12 AM.. Reason: included code to explain myself better
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Redirecting to standard output from within called script

Hi, How to achieve this? Let us assume the following: There are 2 scripts a.ksh and b.ksh $ cat a.ksh sh b.sh 2>&1 >> /work/log/a_log.txt $ cat b.sh echo "abcd" My requirement is, is there a way to display this abcd in standard output also alongside of writing into a_log.txt?... (8 Replies)
Discussion started by: vigneshra
8 Replies

2. UNIX for Dummies Questions & Answers

Return info from a called external script

New to Unix scripting and have written two scripts, one calling the other. When it returns to the calling script is it possible to return information, like a return code? :confused: (1 Reply)
Discussion started by: cathrop
1 Replies

3. UNIX for Dummies Questions & Answers

how to print script output to screen and file

Hi all, I have a script that bulk loads thousands of lines of data. I need to log the output during the execution of the script. I know I can redirect (">") the output to a file; however, I want the output going to both the screen and the log file. I thought I could use pipe to pipe the... (10 Replies)
Discussion started by: orahi001
10 Replies

4. Shell Programming and Scripting

How to return the value from the called shell script to the calling sh script

Hi all, I have two ksh scripts #sample1.sh #!/bin/ksh . ./sample2.sh echo $fileExist #sample2.sh #!/bin/ksh func() { i=1 return $a } func echo $? Here how should I return the value of sample2.sh back to sample1.sh? Thanks in advance. (2 Replies)
Discussion started by: gp_singh
2 Replies

5. Shell Programming and Scripting

return status after run the shell script

Hello, I wanted to delete all files which are placed 14 days back. Here is my below script. My script works very well and it deletes all files 14 days back. I wanted to display message incase if the delete script is not successful. The below script returns always successful. But the directory... (6 Replies)
Discussion started by: govindts
6 Replies

6. Shell Programming and Scripting

Not the correct output, works fine via CLI, not inside the script.

Guys, I need you help please. The script below is not working correclty for checking via a awk/if statement . Can you tell me what i am doing wrong in the script code "if($1 == "$RETENTION_LEVEL") " Syntax RETENTION_LEVEL=`echo $LINE | cut -f2 -d" "` echo " ==============... (4 Replies)
Discussion started by: Junes
4 Replies

7. Shell Programming and Scripting

Return value to shell script, depending on status of pl/sql udpate

Hi All, I need to return value to the main shell script, depending on whether the UPDATE command in the embedded pl/sql is successfu or not. #!bin/ksh updateStatus=`sqlplus --conn details-- << EOF DECLARE var_rows NUMBER; BEGIN update table_name set column_name =... (7 Replies)
Discussion started by: rituparna_gupta
7 Replies

8. Shell Programming and Scripting

Script will keep checking running status of another script and also restart called script at night

I am using blow script :-- #!/bin/bash FIND=$(ps -elf | grep "snmp_trap.sh" | grep -v grep) #check snmp_trap.sh is running or not if then # echo "process found" exit 0; else echo "process not found" exec /home/Ketan_r /snmp_trap.sh 2>&1 & disown -h ... (1 Reply)
Discussion started by: ketanraut
1 Replies

9. Shell Programming and Scripting

Output not in correct format - cd script

I have a script that looks like this: dirname2=/usr/tmp/filelist/*/* for dirname2 in /tmp/filelist/*/*; do (cd $dirname2/catalog ||echo "file does not exist" && echo "$dirname2" |cut -d '/' -f 7,8 && echo $i && ls -la |awk 'NR>3 {SUM += $5} END { print "Total number of kb " SUM }');done... (2 Replies)
Discussion started by: newbie2010
2 Replies

10. Shell Programming and Scripting

Shell script to pass the config file lines as variable on the respective called function on a script

I want to make a config file which contain all the paths. i want to read the config file line by line and pass as an argument on my below function. Replace all the path with reading config path line by line and pass in respective functions. how can i achieve that? Kindly guide. ... (6 Replies)
Discussion started by: sadique.manzar
6 Replies

LEARN ABOUT OSF1

tee

tee(1)							      General Commands Manual							    tee(1)

NAME

       tee - Displays the output of a program and copies it into a file

SYNOPSIS

       tee [-ai] file...

STANDARDS

       Interfaces documented on this reference page conform to industry standards as follows:

       tee:  XCU5.0

       Refer to the standards(5) reference page for more information about industry standards and associated tags.

OPTIONS

       Adds the output to the end of file instead of writing over it.  Ignores the SIGINT signal.

OPERANDS

       Standard input is stored into, or appended to, the file specified.

	      [Tru64 UNIX]  The tee command can accept up to 20 file arguments.

DESCRIPTION

       The tee command reads standard input and writes to both standard output, and each specified file.

       The tee command is useful when you wish to view program output as it is displayed, and also want to save it in a file. The tee command does
       not buffer output, so you may wish to pipe the output of tee to more if more than one full screen of data is anticipated.

NOTES

       If a write to any file fails, the exit status of tee will be non-zero.  Writes to all other specified files may be successful,  and  opera-
       tion will continue until standard input is exhausted.

EXIT STATUS

       The following exit values are returned: Successful completion.  An error occurred.

EXAMPLES

       To view and save the output from a command at the same time, enter: lint program.c | tee program.lint

	      This displays the standard output of the command lint program.c at the terminal, and at the same time saves a copy of it in the file
	      program.lint. If program.lint already exists, it is deleted and replaced.  To display and append to a file, enter: lint program.c  |
	      tee -a program.lint

	      This  displays  the  standard  output of lint program.c at the terminal and at the same time appends a copy of it to the end of pro-
	      gram.lint.  If the file program.lint does not exist, it is created.

ENVIRONMENT VARIABLES

       The following environment variables affect the execution of tee: Provides a default value for the internationalization variables  that  are
       unset or null. If LANG is unset or null, the corresponding value from the default locale is used.  If any of the internationalization vari-
       ables contain an invalid setting, the utility behaves as if none of the variables had been defined.  If set to a  non-empty  string  value,
       overrides  the  values of all the other internationalization variables.	Determines the locale for the interpretation of sequences of bytes
       of text data as characters (for example, single-byte as opposed to multibyte characters in arguments).  Determines the locale for the  for-
       mat  and  contents  of  diagnostic messages written to standard error.  Determines the location of message catalogues for the processing of
       LC_MESSAGES.

SEE ALSO

       Commands:  cat(1), echo(1), script(1)

       Standards:  standards(5)

																	    tee(1)
All times are GMT -4. The time now is 01:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy