solibeam.blogg.se - Flightcheck osx

Flightcheck osx mac os#

Individual Jobs may also specify their own flight checks at submission. It is expected that those files are all proper executables for the platforms on which they are intended to run- otherwise, they will fail and thus jobs will fail. The worker parameter worker_flight_check_path may be set in qb.conf (or nf), to override the default "$QBDIR/flightCheck"Īny file with a ".txt" extension in those subdirectories are ignored, but every other file will be attempted to run at their respective timings.

Flightcheck osx mac os#

Where $QBDIR is the system's Qube install location, which is, by default, "/usr/local/pfx/qube" on Linux, "/Applications/pfx/qube" on Mac OS X, and "C:\Program Files\Pfx\Qube" on Windows.

$QBDIR/flightCheck/agenda/post (agenda-level postflights).

$QBDIR/flightCheck/agenda/pre (agenda-level preflights).

$QBDIR/flightCheck/instance/post (instance-level postflights).

$QBDIR/flightCheck/instance/pre (instance-level preflights).

By default, system-wide flight checks are installed in one of four subdirectories under $QBDIR/flightCheck on the worker. System-wide flight checks are installed by the site administrator into predefined locations on the worker systems, and are run for every job.

The exit codes of flight checks determine the processing and exit status of their respective job instances or agendas. Flight checks, AKA preflights and postflights, new in Qube 6.6, are programs and/or scripts that are run on the worker just before and after the actual job or agenda starts.