On Fri, Jan 24, 2003 at 00:45:38 -0800, David Durst <ddurst@larubber.com> wrote:
>
> I can't be sure that cron will always be up when the DB is up,
> so lets say crond goes down for some random reason (User, System error,
> Etc..)
One option would be to run the cron job fairly often and have it check
if there are any tasks that need to be done. If there are it does them in
a transaction which also makes some update that indicates that the task
has been done.
The other option would be that the process(es) that use the monthly
updates, check to see that they have been done as part of their
transaction and if not do the update first before proceeding.
