The cron tool I have written looks at a local file to determine the last time it has run.
If the file restored after the outage is actually an old version of the file, it will cause the bot to retroactively run processes that it shouldn't run, and could cause headaches for a possibly fragile file system.
Better to run the process manually a few hours after we know everything is stable.
Thanks
Magog
Noted, Magog. The cron daemon is expected to be one of the last services that will come up, and with plenty of advance warning to give everyone an opportunity to do git pulls, reapply changes, etc. If you want, I'll comment out the entries of your tool so that you can turn them back on at leisure?
Coren -
If you have the time, please do. It's quite possible I won't be around for a day or two in time to catch it.