Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Capturing script output and input to log
Top Forums Shell Programming and Scripting Capturing script output and input to log Post 302491550 by Chubler_XL on Thursday 27th of January 2011 05:32:44 PM
Old 01-27-2011
OK well best to edit your script and put the stuff you want to log in a function and pipe it to tee:

Code:
function display_menu
{
 ....
}
 
function doprocessing
{
   ....
}
 
# main code block
display_menu
...
doprocessing | tee output.log

or put your processing code between ( ) and redirect this output to tee ( ... ) | tee output.log

These are generic solutions and perhaps a simplified example of your script will help us to give a more specific solution.
Last edited by Chubler_XL; 01-27-2011 at 07:03 PM.. Reason: Syntax update - support bash or ksh
This User Gave Thanks to Chubler_XL For This Post:
methyl
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

capturing output in script

I have the following line in my script: $sftpcmd $rmthost <<COMMANDS>> $sftplog 2>&1 For some reason this is not capturing the errors from sftp, they go to the file attached to the cron entry ie mm hh dd MM * /myscript > cron.out any idea why? digital unix 4.0d (6 Replies)
Discussion started by: MizzGail
6 Replies

2. Shell Programming and Scripting

Capturing shell script command output

I am trying to check to see if a file exists on a ftp server, well, I know that cant be done, atleast directly, So I came up with this small script ftp -n $HOST <<END_SCRIPT quote USER $USER quote PASS $PASSWD cd public_html/crap dir $FILE quit END_SCRIPT Where the $ variable... (2 Replies)
Discussion started by: designflaw
2 Replies

3. Shell Programming and Scripting

log script input and output using tee ?

hi, new to to forum... i've been trying to create a script in tcsh but i'm having a problem with one thing... the script has to keep log of it's input and output so i'm using tee -a log | script | tee -a log this keeps the logs as asked, but it gives me an extra empty prompt (not in the... (0 Replies)
Discussion started by: moseschrist
0 Replies

4. Shell Programming and Scripting

capturing line from script output and appending to a file

Hi all, I did some searching in this forum but can't find anything that matches the issue I'm bumping heads with. On a CentOS4/Postfix (and bash everywhere) mail gateway box I run a command periodically to purge the Postfix queue of messages "From:MAILER-DAEMON". This is the one line'r... (6 Replies)
Discussion started by: wally_welder
6 Replies

5. Shell Programming and Scripting

Capturing Sybase SP output in Shell Script

Greetings, I need to capture the output of a Sybase stored procedure, inside my shell script( k shell). Based on this output, I need to call another perl script, with input arguments as the result set of the procedure execution. I need to keep looping through and call the perl script, ... (2 Replies)
Discussion started by: rajpreetsidhu
2 Replies

6. UNIX for Dummies Questions & Answers

Capturing Input Parameters on Shell Script

i have this basic line of code that doesn't work. i simply want to get the input parameter strings but when the script is run it appears that the first parameter is assigning the value to the second parameter. #!/bin/sh pdir=`pwd` p1=$1 p2=$2 echo "directory: $pdir\n" echo "parameter... (2 Replies)
Discussion started by: wtolentino
2 Replies

7. Shell Programming and Scripting

Problem capturing output in TCL script

I have a TCL script that logs into a switch using expect.I send a command "show port-security address" and it returns a table having a large number of rows.I need to capture this output(the table) and store it in a .txt file. I have done this: match_max 5000 set expect_out(buffer) {} set... (0 Replies)
Discussion started by: plasmalightwave
0 Replies

8. Shell Programming and Scripting

Capturing log of a shell script

Hi, I have a script which does multiple tasks in sequence. When i execute the script, it runs and displays lot of messages for each of the steps on the console. Is there any way I can capture those messages and store it for audit purposes ? Best Regards, bornon2303 (2 Replies)
Discussion started by: bornon2303
2 Replies

9. Shell Programming and Scripting

Capturing output of procedure in variable in shell script

Hi guys I am calling one DB2 stored proc through unix. It is giving me below output. I want to capture the value 150 in one UNIX variable in shell script. Please let me know how I can achieve this. Thanks in advance Value of output parameters -------------------------- Parameter Name :... (5 Replies)
Discussion started by: vnimavat
5 Replies

10. Shell Programming and Scripting

Help capturing output of expect script

match_max 500000 set timeout 30 set outcome1 {} set outcome2 {} set inputfile C:\\Users\\Administrator\\Desktop\\inputfile.txt send -i $con "\r"; expect -i $con "Desktop>" { exp_send "type $inputfile \r" } set timeout 30 expect { "Desktop>" { set outcome $expect_out(0,string);}... (3 Replies)
Discussion started by: cityprince143
3 Replies

LEARN ABOUT OPENSOLARIS

tee

tee(1)								   User Commands							    tee(1)

NAME

       tee - replicate the standard output

SYNOPSIS

   /usr/bin/tee
       /usr/bin/tee [-ai] [file]...

   ksh93
       tee [-ail] [file]...

DESCRIPTION

   /usr/bin/tee
       /usr/bin/tee  copies  standard  input  to standard output, making a copy in zero or more files. tee does not buffer its output. The options
       determine if the specified files are overwritten or appended to.

   ksh93
       The tee built-in in ksh93 is associated with the /bin and /usr/bin paths. It is invoked when tee is executed without a pathname prefix  and
       the pathname search finds a /bin/tee or /usr/bin/tee executable.

       tee  copies  standard input to standard output and to zero or more files. The options determine whether the specified files are overwritten
       or appended to. The tee utility does not buffer output. If a write to a file fails, tee continues to write to other files although it exits
       with a non-zero exit status.

       The number of file operands that can be specified is limited by the underlying operating system.

OPTIONS

   /usr/bin/tee
       The following options are supported by /usr/bin/tee:

       -a    Appends the output to the files rather than overwriting them.

       -i    Ignores interrupts.

   ksh93
       The following options are supported by the tee built-in command in ksh93:

       -a		      Appends the output to the files rather than overwriting them.
       --append

       -i		      Ignores SIGINT signal.
       --ignore-interrupts

       -l		      Sets the standard output to be line buffered.
       --line-buffer

OPERANDS

       The following operands are supported:

       file    A path name of an output file. Processing of at least 13 file operands are supported.

USAGE

       See largefile(5) for the description of the behavior of tee when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).

ENVIRONMENT VARIABLES

       See  environ(5)	for  descriptions of the following environment variables that affect the execution of tee: LANG, LC_ALL, LC_CTYPE, LC_MES-
       SAGES, and NLSPATH.

EXIT STATUS

   /usr/bin/tee
       The following exit values are returned by /usr/bin/tee:

       0     The standard input was successfully copied to all output files.

       >0    The number of files that could not be opened or whose status could not be obtained.

   ksh93
       The following exit values are returned by tee in ksh93:

       0     Successful completion.

       >0    An error occurred.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

   /usr/bin/tee
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+
       |CSI			     |Enabled			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Committed 		   |
       +-----------------------------+-----------------------------+
       |Standard		     |See standards(5). 	   |
       +-----------------------------+-----------------------------+

   ksh93
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |See below.		   |
       +-----------------------------+-----------------------------+

       The ksh93 built-in binding to /bin and /usr/bin is Volatile. The built-in interfaces are Uncommitted.

SEE ALSO

       cat(1), ksh93(1), attributes(5), environ(5), largefile(5), standards(5)

SunOS 5.11							    20 Nov 2007 							    tee(1)
All times are GMT -4. The time now is 10:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy