[ http://issues.apache.org/jira/browse/GUMP-66?page=all ]
Leo Simons closed GUMP-66:
--------------------------
Resolution: Fixed
Assign To: Leo Simons
Gump3's locking is doing just fine. Its a simple matter of firing off gump
continuously from cron now:
* * * * * cd /usr/local/gump/gump3/Gump3/; /usr/bin/nice /bin/bash gump
run --do-updates --do-builds --databasename=gump3 --irc='[EMAIL
PROTECTED]/#asfgump' --debug >/dev/null 2>/dev/null
similar stuff could of course be done using "batch" or "at", but I think this
is just fine. Of course I haven't set gump3 up that way right now as it'd be
kinda verbose on IRC and generate lots of log messages. But its possible.
> Run gump as a service
> ---------------------
>
> Key: GUMP-66
> URL: http://issues.apache.org/jira/browse/GUMP-66
> Project: Gump
> Type: New Feature
> Components: Python-based Gump
> Versions: Gump2-2.4
> Environment: Brutus (and similar)
> Reporter: Adam Jack
> Assignee: Leo Simons
> Priority: Minor
> Fix For: Gump3-alpha-5
>
> 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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
