Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Writing a UNIX script from LOG to provide return code.
Top Forums Shell Programming and Scripting Writing a UNIX script from LOG to provide return code. Post 302512893 by KenJackson on Monday 11th of April 2011 08:48:42 PM
Old 04-11-2011
Is there only one execution completed per log file? Or are there multiple executions?
If there's only one, then it's pretty simple.

Also, I assume you mean to return a binary return code, not text to stdout.

Code:
#!/bin/sh
test -f "$1"  &&  grep -q 'execution completed successfully' "$1"

Put that in a file, maybe name it checklog, use chmod to make it executable and use it like this:

checklog logfile

If the argument file doesn't exist, test -f will return 1 without doing the grep.
If the file exists and the quoted text is not found, grep will quietly return 1.
If both tests succeed, 0 is returned.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Need help in writing a unix script

OS: Solaris Shell : KSH Please help me in writing a script that captures a error message from a log file ( which updates continiously ) and send an email alert as soon as the systems throws a error message into that log. i.e With out monitoring the log Thanks in advance.. (1 Reply)
Discussion started by: pray44u
1 Replies

2. Shell Programming and Scripting

return code of a unix command

How to find out whether the command I executed is successful or unsuccessful(at commandlinet) Eg: say i execute the following command at command line rm * How do i find out whether my previous command is a success or failure. Thankyou. Best Regards, Ram. (1 Reply)
Discussion started by: ramky79
1 Replies

3. Shell Programming and Scripting

return code from script

hey all, I have a simple script #!/bin/bash ./cron.sh test_a.txt & ./cron.sh test_b.txt & wait I want to invoke another program based on the return status of the above calls. How am I were to get that? Thanks! (2 Replies)
Discussion started by: mpang_
2 Replies

4. UNIX for Dummies Questions & Answers

Perl Unix Script Writing

Hi Folks, I posted a few days ago, thanks for the responses. My original question was for renaming files of sort 3p2325294.dgn in a directory containing multiple files. I need to drop the first 2 characters and the last in a unix script using Perl. How does it differ from using the Unix... (1 Reply)
Discussion started by: Dinkster
1 Replies

5. Shell Programming and Scripting

help writing this unix script

I am working on writing scripts. Here is a script I need help with. I have also wrote what I think it is. I would really appreciate any help that I can get. Create an executable script file called "newname" that will perform the followings: 1. Rename a file upon the user's request. If the... (2 Replies)
Discussion started by: wiggles
2 Replies

6. Shell Programming and Scripting

need help writing this unix script

Create an executable script file called "newname" that will perform the followings: 1. Rename a file upon the user's request. If the file exists, prompt the user for confirmation before renaming the file. The screen should prompt the user for a. "Name of file you want to rename." Use the "\c"... (7 Replies)
Discussion started by: wiggles
7 Replies

7. Shell Programming and Scripting

Pointers on writing a unix script

Hi All, I am writing a unix shell script. I have a file called Results.txt which stores 4 fields separated by pipe. i.e. a pipe delimited file. I want to loop through each record of this file and store each of these 4 fields into variables. I have read can be done through awk but I have never... (7 Replies)
Discussion started by: shwetainnani
7 Replies

8. HP-UX

return code from oracle to unix script

Hi I'm writing a shell script that connects to oracle database and fires query to check the availability of data in a table. In case of no data found then what will be the return code and how to handle in that in variable. Kindly provide with an example for better understanding... Thanks... (1 Reply)
Discussion started by: ksailesh
1 Replies

9. Shell Programming and Scripting

Unix return code example

Hi, Does anyone here can guide me to understand how is return code works in a parent-child relation with a simple example? I have a request to build the script with return code in a child script, but i want to understand how does child script can return a code to the parent, stated if its... (4 Replies)
Discussion started by: khchong
4 Replies

10. Shell Programming and Scripting

Need to get return code from mutt if an address is invalid/undeliverable from Unix shell script

I am using mutt on ksh Unix to send emails to addresses plucked from the database. If the "To:" email address is not longer valid and so the email is not sent to the "To:" recipient, but is sent to the valid cc address, I need to be able to get an error code returned to the shell script so that... (3 Replies)
Discussion started by: jzuber
3 Replies

LEARN ABOUT OSF1

sh

sh(1)							      General Commands Manual							     sh(1)

NAME

       sh - Shell, the standard command language interpreter

DESCRIPTION

       [Tru64  UNIX]  Tru64  UNIX  provides two command interpreters with the name sh.	The XCU5.0 and POSIX.2 compliant command interpreter sh is
       available in the file /usr/bin/posix/sh and is described in the sh(1p) reference page.  The Bourne shell,  historically	known  as  sh,	is
       available in the file /usr/bin/sh and is described in the sh(1b) reference page.

       [Tru64 UNIX]  Your initial, or login, shell is determined by your entry in the file /etc/passwd. This file can be changed only by your sys-
       tem administrator. You must use whatever procedures are in place at your location to have this entry changed.

       [Tru64 UNIX]  If available on your system, you may use the passwd -s or the chsh commands to change your login shell.

									  Note

       This option is not available if your site manages passwords through the Network Information Service (NIS) facility.  Check with your system
       administrator.

       [Tru64 UNIX]  Subsequent shells spawned from the initial shell depend on the value in the environment variable BIN_SH.  If this variable is
       set to xpg4, the POSIX shell is started. If this variable is set to svr4, an SVR4 compliant version of the shell is started. If this  vari-
       able  is  unset,  the  Bourne shell is started. If this variable is set to any other value, an error is reported and the results are unpre-
       dictable. See the EXAMPLES section for information on setting this variable.

NOTES

       [Tru64 UNIX]  With Tru64 UNIX Version 4.0 the Korn shell, /usr/bin/ksh is the same as the POSIX shell /usr/bin/posix/sh.

RESTRICTIONS

       [Tru64 UNIX]  The file /etc/shells must include entries for both the POSIX shell /usr/bin/posix/sh and the Bourne  shell,  /usr/bin/sh.	If
       this file is incorrect, see your system administrator.

EXAMPLES

       Using  the  Bourne,  Korn,  or  POSIX  shell, to set the variable BIN_SH to use the POSIX/ XCU5.0compliant shell, enter: BIN_SH=xpg4 export
       BIN_SH Using the Bourne, Korn, or POSIX shell, to set the variable BIN_SH to use the SVR4 compliant shell, enter: BIN_SH=svr4 export BIN_SH
       Using the Bourne, Korn, or POSIX shell, to unset the variable BIN_SH, enter: unset BIN_SH Using the C/ shell, to set the variable BIN_SH to
       use the POSIX/XCU5.0 compliant shell, enter: setenv BIN_SH xpg4 Using the C/ shell, to set the variable BIN_SH to use  the  SVR4  compliant
       shell, enter: setenv BIN_SH svr4 Using the C/ shell, to unset the variable BIN_SH, enter: unsetenv BIN_SH

FILES

       User profile.  Contains user information, including the login shell name.  Contains the names of available and permitted shells.

SEE ALSO

       Commands:  csh(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p), passwd(1)

       Files:  passwd(4), shells(4)

       Standards:  standards(5)

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