Thanks for the detailed kill instructions; but it still doesn't work. See terminal below:
Paul-Denlingers-MacBook-Pro:blog3 pdenlinger$ rails server /Library/Ruby/Gems/1.8/gems/bundler-1.0.0/lib/bundler/runtime.rb:134: warning: Insecure world writable dir /Library/Ruby/Gems/1.8 in PATH, mode 040777 => Booting WEBrick => Rails 3.0.0 application starting in development on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server [2010-08-30 19:56:21] INFO WEBrick 1.3.1 [2010-08-30 19:56:21] INFO ruby 1.8.7 (2009-06-12) [universal- darwin10.0] [2010-08-30 19:56:21] INFO WEBrick::HTTPServer#start: pid=42417 port=3000 pkill ps aux | grep rails | awk '{print $2}' | xargs kill -9 ps aux|grep rails|awk'{print$2}'|xargs kill -9 Started GET "/home/index" for 127.0.0.1 at Mon Aug 30 19:59:23 +0800 2010 ActionController::RoutingError (No route matches "/home/index"): Rendered /Library/Ruby/Gems/1.8/gems/actionpack-3.0.0/lib/ action_dispatch/middleware/templates/rescues/routing_error.erb within rescues/layout (1.0ms) Paul-Denlingers-MacBook-Pro:blog3 pdenlinger$ rails server /Library/Ruby/Gems/1.8/gems/bundler-1.0.0/lib/bundler/runtime.rb:134: warning: Insecure world writable dir /Library/Ruby/Gems/1.8 in PATH, mode 040777 => Booting WEBrick => Rails 3.0.0 application starting in development on http://0.0.0.0:3000 => Call with -d to detach => Ctrl-C to shutdown server [2010-08-30 19:56:21] INFO WEBrick 1.3.1 [2010-08-30 19:56:21] INFO ruby 1.8.7 (2009-06-12) [universal- darwin10.0] [2010-08-30 19:56:21] INFO WEBrick::HTTPServer#start: pid=42417 port=3000 pkill ps aux | grep rails | awk '{print $2}' | xargs kill -9 Don't see how the server seemed to boot up again all by itself. Is it possible to remove Ruby and Rails and do a clean install? Paul Denlinger On Aug 30, 1:33 pm, Chris Winslett <[email protected]> wrote: > > When I hit Command-C to quit the server, nothing happened > > either. > > Try control + c. That'll do donkey. That'll do. > > If that doesn't work, you could always do the following (assuming you > don't have 'pkill' installed): > > ps aux | grep rails | awk '{print $2}' | xargs kill -9 > > If you want to shorten that to "kill_rails" you could do the > following, restart your terminal, and always 'kill rails' efficiently: > > echo "alias kill_rails='ps aux | grep rails | awk '{print $2}' | > xargs kill -9'" >> ~/.bashrc > > The cool thing about stopping processes with a Mac is: there is more > than one way to kill a daemon. > > Chris > > On Aug 29, 7:11 pm, pauld <[email protected]> wrote: > > > > > After Rails 3 was just released today, I downloaded it and followed > > the instructions on Rails Guide for building my first app at Getting > > Started with Railshttp://guides.rubyonrails.org/getting_started.html > > > Everything worked fine until I got to 4.2 Say "Hello" Rails. Entered > > the "rails generate home controller index" command, and nothing > > happened. When I hit Command-C to quit the server, nothing happened > > either. > > > No error messages. > > > What happened? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
