task_schedule_gap.cfg

# Configuration file for task_schedule.pl to run astromon jobs

subject           Engineering telemetry archive
timeout           80000             # Default tool timeout
heartbeat_timeout 10                # Maximum age of heartbeat file (seconds)
iterations        1                 # Run once then shut down task_schedule
print_error       1                 # Print full log of errors
disable_alerts    0                 # Don't disable alerts since this jobs runs just once/day
loud              0                 # Run loudly or quietly (production mode)

# Data files and directories.  The *_dir vars can have $ENV{} vars which
# get interpolated.  (Note lack of task name after TST_DATA because this is just for test).

data_dir     $ENV{SKA_DATA}/eng_archive       # Data file directory
log_dir      $ENV{SKA_DATA}/eng_archive/logs  # Log file directory
bin_dir      $ENV{SKA_SHARE}/eng_archive      # Bin dir (optional, see task def'n)
master_log   eng_archive.log             # Composite master log (created in log_dir)

# Email addresses that receive an alert if there was a severe error in
# running jobs (i.e. couldn't start jobs or couldn't open log file).
# Processing errors *within* the jobs are caught with watch_cron_logs

alert       aca@head.cfa.harvard.edu

# Define task parameters
#  cron: Job repetition specification ala crontab
#  exec: Name of executable.  Can have $ENV{} vars which get interpolated.
#        If bin_dir is defined then bin_dir is prepended to non-absolute exec names.
#  log: Name of log.  Can have $ENV{} vars which get interpolated.
#        If log is set to '' then no log file will be created
#        If log is not defined it is set to <task_name>.log.
#        If log_dir is defined then log_dir is prepended to non-absolute log names.
#  timeout: Maximum time (seconds) for job before timing out

# This has multiple jobs which get run in specified order
# Note the syntax 'exec <number> : cmd', which means that the given command is
# executed only once for each <number> of times the task is executed.  In the
# example below, the commands are done once each 1, 2, and 4 minutes, respectively.

<task eng_archive>
      cron       * * * * *
      check_cron * * * * *
      exec update_archive.py --data-root /proj/sot/ska/data/eng_archive --max-gap 1000000
      exec transfer_stage.py --data-root /proj/sot/ska/data/eng_archive
      <check>
        <error>
          #    File           Expression
          #  ----------      ---------------------------
             eng_archive.log     error
             eng_archive.log     warning
             eng_archive.log     fatal
        </error>
      </check>
</task>