Details
-
New Feature
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
Gump2-2.4
-
None
-
Brutus (and similar)
Description
Currently Gump runs from cron, at intervals, if Gump is not still running (from a previous run). This is somewhat haphazard, and a waste of spare cycles. Gump needs to be able to be run continuously, starting a new run a soon as the last has completed. This seems like some sort of 'service' script, but it is likely OS specific.
The script that runs this countinuously could call gumpy.sh (or gumpy.py) and launch runs with varied commandline parameters. For example, it could make every Nth run an official run, or make N-1 'optimized' (only compile if something changed) and the Nth full, etc.