3.5 Cron Job Installation

Once all DB creation, modification and customization are done, you are ready to submit cron jobs for the following scripts:

• hdf5perf/hdf5perfphp/run_1.6.sh

• hdf5perf/hdf5perfphp/run_1.8.sh

• hdf5perf/hdf5perfphp/run_1.9.sh

• php hdf5perf/hdf5perfphp/hdf/sync.php

• php hdf5perf/hdf5perfphp/hdf/mailer.php

Here's an example cron job table listing on hdfdap.hdfgroup.uiuc.edu machine at The HDF Group:

    00 18 * * * /hdf5perf/hdf5perfphp/run_1.6.sh
    00 20 * * * /hdf5perf/hdf5perfphp/run_1.8.sh
    00 22 * * * /hdf5perf/hdf5perfphp/run_1.9.sh
    15 01 * * * /usr/bin/php /hdf5perf/hdf5perfphp/hdf/sync.php
    55 01 * * * /usr/bin/php /hdf5perf/hdf5perfphp/hdf/mailer.php

The above example tells us that the HDF5 library version 1.6 testing starts at 6:00pm, HDF5 library version 1.8 at 8:00pm and version 1.9 at 10:00pm on hdfdap.hdfgroup.uiuc.edu machine.

You should not install the sync.php and mailer.php cron jobs for the machines (e.g., linew, smirom and jam) that do not run the HPF MySQL database since they need to be run only once from the machine that collects all data using a MySQL database.

The sync.php cleans up any duplicate entries from the routine and action tables in the database and ensure that the front-end system can run smoothly.

The mailer.php script sends an e-mail notification to subscribers if there is a significant increase in performance.