From dacbf8bc0133f21d9f7a4ec7ec149e57d8d05ad1 Mon Sep 17 00:00:00 2001 From: jonsowman Date: Fri, 23 Jul 2010 12:21:31 +0100 Subject: [PATCH] explained re-running and TTL --- README.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.markdown b/README.markdown index 0ee1b96..75ae7cb 100644 --- a/README.markdown +++ b/README.markdown @@ -21,7 +21,7 @@ There are useful configuration options in `predict/includes/config.inc.php`. ## Information -The two bash scripts in the `cron/` directory should both be run daily. `clear-pydap-cache-cronjob.sh` clears the cache used by pydap so that old data does not build up. `purge-predictions-cronjob.sh` deletes scenarios and predictions not accessed or modified within the last 7 days. +The two bash scripts in the `cron/` directory should both be run daily. `clear-pydap-cache-cronjob.sh` clears the cache used by pydap so that old data does not build up. `purge-predictions-cronjob.sh` deletes scenarios and predictions not accessed or modified within the last 7 days. Re-running a prediction for a scenario will therefore reset its time to live to 7 more days. The directory names are UUIDs comprised of an SHA1 hash of the launch parameters, and re-running predictions will overwrite data in the existing directory, rather than create a new one.