[ http://issues.apache.org/jira/browse/GUMP-66?page=history ]
Leo Simons updated GUMP-66:
---------------------------
Version: unspecified
> Run gump as a service
> ---------------------
>
> Key: GUMP-66
> URL: http://issues.apache.org/jira/browse/GUMP-66
> Project: Gump
> Type: New Feature
> Components: Infrastructure
> Versions: unspecified
> Environment: Brutus (and similar)
> Reporter: Adam Jack
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
