January 8, 2009 11:46pm pst

1. ozo 225

1. ozo 84,020
2. Tintin 77,014
3. omarfarid 51,706
4. ghostdog74 19,525
5. sentner 15,500
6. MikeOM_... 12,900
7. Adam314 9,400
8. amit_g 8,236
9. ahoffmann 7,725
10. sunnycoder 7,272
11. gheist 5,614
12. sjm_ee 5,500
13. johnsone 5,300
14. JustUNIX 5,000
15. nognew 2,800
16. marchent 2,600
17. jools 2,560
18. oklit 2,500
19. nixfreak 2,375
20. RSLE 2,100
21. blu 2,000
21. tfewster 2,000
21. murugesa... 2,000
21. awking00 2,000
21. amnonnes 2,000
21. just-Dave 2,000
21. MentorJay 2,000
21. hernst42 2,000
21. Milleniuma... 2,000
21. sdstuber 2,000
21. FishMonger 2,000
21. fridom 2,000

07.18.2008 at 02:21AM PDT, ID: 23576208

	[x] Attachment Details

Unix Exit Codes

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.9

Zones:

KornShell (ksh), Linux, Shell Scripting

Hi,

I'm using a script to start my application on a daily basis. A cron-like application called Control-M calls this script at a give time and starts the app. The script istelf is very simple as you can see below.

However the line "Load app" occasionally has thrown an error which has resulted in "app.sh" failing to start up the applicartion. I need to check the "Load app" command has completed successfully before calling app.sh, otherwise abort.

How can I do this? Some one mention using exit codes, but I don't know how this works. any ideas?

         
             #!/bin/ksh
. /apps/bin/0LOAD
Load app
app.sh

Start your 7 day free trial to see this answer

Answered By:	Tintin
Expert Since:	11/13/2002
Accepted Solutions:	3706

Tintin has been an Expert for 6 years1 month, during which he has posted 13256 comments and answered 3706 questions. Tintin is just one of 97 experts in the KornShell (ksh) Zone. 4 experts collaborated on this answer, which was graded an "A" by the asker.

#	Title
1	Linux/Unix cron automation
2	Execute a PHP script every 2 mins
3	Using Cron with a holiday file?
4	Unix Shell script query
5	Sample scripts for CRON JOBS
6	Abortion