Good point! Both of them. That would make a not-so-quick but better hack. Append a timestamp and a start note / end note with exit code to a log file, to have a history. You might also send an email in case of a crash. Let's see ...

#!/bin/sh
while true
do
  start_your_program
  RC=$?          # return code
  if [ $RC -gt 0 ]
  then
    date >> /var/log/your_log_file
    echo "ABNORMAL program termination, rc = $RC" >> /var/log/your_log
+_file
    echo "terminated at `date`, restarting | mail -s "Problem with zzz
+" root
    sleep xxx
  else
    date >> /var/log/your_log_file
    echo "Normal program termination, rc = $RC" >> /var/log/your_log_f
+ile
    sleep yyy
  fi
done
[download]

You can do further checking on the exit code as Mark suggested and act diffently according to the exit code (see case statement in your shell manual).

Andreas

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.