You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2005/03/24 01:46:18 UTC

[JIRA] Commented: (FOR-364) Add Ctrl-C-Info to Jetty Startup-Messages

The following comment has been added to this issue:

     Author: David Crossley
    Created: Wed, 23 Mar 2005 6:44 PM
       Body:
A basic message has been added to the 'forrest run' startup.

I don't understand the remainder of your suggestion: "trigger the query" and "answer the following question" ... i don't see that behaviour on UNIX.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-364?page=comments#action_12174

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-364

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-364
    Summary: Add Ctrl-C-Info to Jetty Startup-Messages
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Forrest
 Components: 
             Launch 'forrest run'

   Assignee: 
   Reporter: Ferdinand Soethe

    Created: Thu, 11 Nov 2004 3:34 AM
    Updated: Wed, 23 Mar 2005 6:44 PM

Description:
At the moment it is guesswork how to properly end a "forrest run" session. Even more confusing that Ctrl-C (the only way to do it) will also trigger the query if you want to abort batch processing.

A short info that is written just before the server is active should inform the user about the proper procedure:

"To stop the Forrest/Jetty server, press Ctrl-C, answer [N]o to the following question and press Enter to confirm."


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira