Return-Path: Delivered-To: apmail-gump-general-archive@www.apache.org Received: (qmail 5033 invoked from network); 18 Jun 2004 14:14:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 18 Jun 2004 14:14:22 -0000 Received: (qmail 41826 invoked by uid 500); 18 Jun 2004 14:14:14 -0000 Delivered-To: apmail-gump-general-archive@gump.apache.org Received: (qmail 41564 invoked by uid 500); 18 Jun 2004 14:14:10 -0000 Mailing-List: contact general-help@gump.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Gump code and data" Reply-To: "Gump code and data" Delivered-To: mailing list general@gump.apache.org Received: (qmail 41473 invoked by uid 99); 18 Jun 2004 14:14:09 -0000 Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.27.1) with SMTP; Fri, 18 Jun 2004 07:14:08 -0700 Received: (qmail 26450 invoked from network); 18 Jun 2004 14:15:10 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 18 Jun 2004 14:15:10 -0000 Message-ID: <2139556110.1087568109996.JavaMail.apache@nagoya> Date: Fri, 18 Jun 2004 07:15:09 -0700 (PDT) From: general@gump.apache.org To: general@gump.apache.org Subject: [jira] Created: (GUMP-66) Run gump as a service Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Message: A new issue has been created in JIRA. --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/GUMP-66 Here is an overview of the issue: --------------------------------------------------------------------- Key: GUMP-66 Summary: Run gump as a service Type: New Feature Status: Unassigned Priority: Major Project: Gump Components: configuration of live servers Assignee: Reporter: Adam Jack Created: Fri, 18 Jun 2004 7:14 AM Updated: Fri, 18 Jun 2004 7:14 AM Environment: 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. --------------------------------------------------------------------- JIRA INFORMATION: 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: general-unsubscribe@gump.apache.org For additional commands, e-mail: general-help@gump.apache.org