<p>You could also do what we have at work. A simple bash script that wraps the execution on each cron job with a kind on is it running check based off of a file with its pid being dropped to file system. If it exesists don't execute the cron and wait for the next execution.</p>
<p><blockquote type="cite">On Dec 29, 2009 2:19 PM, "Shawn Perry" <<a href="mailto:redmop924@comcast.net">redmop924@comcast.net</a>> wrote:<br><br>fcron is awesome. the serialonce job option should handle what you're looking for.<p>
<font color="#500050">
On Tue, Dec 29, 2009 at 1:21 PM, Collins Richey <<a href="mailto:crichey@gmail.com">crichey@gmail.com</a>> wrote:
>
> On Tue, Dec 29, 200...</font></p><br>_______________________________________________<br>
clue-tech mailing list<br>
<a href="mailto:clue-tech@cluedenver.org">clue-tech@cluedenver.org</a><br>
<a href="http://www.cluedenver.org/mailman/listinfo/clue-tech" target="_blank">http://www.cluedenver.org/mailman/listinfo/clue-tech</a><br></blockquote></p>