2.  How to automate downloading work-units and uploading results

 Last updated 2001/07/01 15:00 UTC

1st appeared 2001/01/07 17:00 UTC

I am using FetchCache and RunCache shell scripts introduced on the FAQ page of seti@home.

In June of 2001, I introduced ever-connecting Internet connetctions to my home. But, I use this WU-caching to prepare for the frequent outage of the seti-server at UC Berkely.

 Up/Downloading Scripts = FetchCache driven by crond in staggered time

  Crond schedules FetchCache in night period to upload results and to download work-units. Each CETI-machine starts FetchCache at different time.

 Running Scripts = RunCache started regularly by crond

  RunCache does analysis. Crond is configured to scheduled RunCache at every 5 minutes to restart its task, because it stops after going around all the downloaded work-units. This scheduling is also effective at machine reboot and unexpected failure.

 Dialup environment = automatic dialing only in low-cost night-period("TeleHodai" time)

  My Terminal Adapter dials to my ISP automatically when any IP packet destined for the Internet appears. But TA is configured to allow this action only in night period (23:00 to 8:00). In this period, cost of telephone call to my ISP is not related to the connection-time length, because I subscribed in NTT's "Tele-Hodai" option. Outside of this period, I must pay 10 yen(9 cents) per 3 minutes for local call.

  So, FetchCache must be spawned in this period. Combination of FetchCache and RunCache enable me to make CETI-machines constantly busy for analysis at minimum cost of using telephone.