> 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.
