Backed out of script/run portal idea. Muscle memory too deep

git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@2469 5ecf4fe2-1ee6-0310-87b1-e25e094e27de

1 files changed, 3 insertions, 4 deletions

diff --git a/railties/lib/commands/process/reaper.rb b/railties/lib/commands/process/reaper.rb
index 27c05ed5ce..b5b82c310f 100644
--- a/railties/lib/commands/process/reaper.rb
+++ b/railties/lib/commands/process/reaper.rb
@@ -77,19 +77,18 @@ ARGV.options do |opts|
 
   opts.on <<-EOF
   Description:
-    The reaper is used to reload, gracefully exit, and forcefully exit FCGI processes
+    The reaper is used to restart, reload, gracefully exit, and forcefully exit FCGI processes
     running a Rails Dispatcher. This is commonly done when a new version of the application
     is available, so the existing processes can be updated to use the latest code.
 
     The reaper actions are:
 
+    * restart : Restarts the application by reloading both application and framework code
     * reload  : Only reloads the application, but not the framework (like the development environment)
     * graceful: Marks all of the processes for exit after the next request
     * kill    : Forcefully exists all processes regardless of whether they're currently serving a request
 
-    Graceful exist is the most common and default action. But since the processes won't exist until after
-    their next request, it's often necessary to ensure that such a request occurs right after they've been
-    marked. That's what nudging is for. 
+    Restart is the most common and default action.
 
     A nudge is simply a request to a URL where the dispatcher is serving. You should perform one nudge per
     FCGI process you have running if they're setup in a round-robin. Be sure to do one nudge per FCGI process