I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in my VPS hosting account
on eApps.com. I''ve tried to install Rails several times, without
success. I then went through the following sequence:
# gem install rails --include-dependencies
INFO: `gem install -y` is now default and will be removed
INFO: use --ignore-dependencies to install only the gems you list
Updating metadata for 476 gems from http://gems.rubyforge.org/
.................................................................................................<snip>
complete
Bulk updating Gem source index for: http://gems.rubyforge.org/
Terminated
# gem install rails --include-dependencies
INFO: `gem install -y` is now default and will be removed
INFO: use --ignore-dependencies to install only the gems you list
Bulk updating Gem source index for: http://gems.rubyforge.org/
Successfully installed rake-0.8.1
Successfully installed activesupport-2.1.0
Successfully installed activerecord-2.1.0
Successfully installed actionpack-2.1.0
Successfully installed actionmailer-2.1.0
Successfully installed activeresource-2.1.0
Successfully installed rails-2.1.0
7 gems installed
Installing ri documentation for rake-0.8.1...
Installing ri documentation for activesupport-2.1.0...
RDoc failure in lib/active_support/core_ext/class/removal.rb at or
around line 37 column 19
Before reporting this, could you check that the file
you''re documenting compiles cleanly--RDoc is not a
full Ruby parser, and gets confused easily if fed
invalid programs.
The internal error was:
Terminated
# gem install rails
Bulk updating Gem source index for: http://gems.rubyforge.org/
Killed
# gem install rails
Bulk updating Gem source index for: http://gems.rubyforge.org/
Killed
# gem --debug install rails
Exception `NameError'' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/
command_manager.rb:133 - uninitialized constant
Gem::Commands::InstallCommand
Exception `Gem::LoadError'' at /usr/local/lib/ruby/site_ruby/1.8/
rubygems.rb:523 - Could not find RubyGem sources (> 0.0.1)
Exception `EOFError'' at /usr/local/lib/ruby/1.8/net/protocol.rb:133 -
end of file reached
Exception `EOFError'' at /usr/local/lib/ruby/1.8/net/protocol.rb:120 -
end of file reached
Bulk updating Gem source index for: http://gems.rubyforge.org/
Killed
# gem uninstall rails
Successfully uninstalled rails-2.1.0
Remove executables:
rails
in addition to the gem? [Yn] y
Removing rails
# gem install rails
Bulk updating Gem source index for: http://gems.rubyforge.org/
Killed
Now every time I try the last command, it fails the same way. Any
suggestions?
--~--~---------~--~----~------------~-------~--~----~
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
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
khurrum1-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
2008-Jul-17 21:06 UTC
Re: Rails install failure on VPS host - suggestions?
Is it possible that there is a process running on the server that is detecting high processor utilization due to the gem install and killing the gem process automatically? Maybe you can run tail -f /var/log/messages in a separate terminal window and then run the gem install in another window for clues as to what is causing the gem process to get killed. I''m just guessing :) I may be very wrong. On Jul 17, 3:59 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote:> I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in my VPS hosting account > on eApps.com. I''ve tried to install Rails several times, without > success. I then went through the following sequence: > > # gem install rails --include-dependencies > INFO: `gem install -y` is now default and will be removed > INFO: use --ignore-dependencies to install only the gems you list > Updating metadata for 476 gems fromhttp://gems.rubyforge.org/ > .................................................................................................<snip> > complete > Bulk updating Gem source index for:http://gems.rubyforge.org/ > Terminated > > # gem install rails --include-dependencies > INFO: `gem install -y` is now default and will be removed > INFO: use --ignore-dependencies to install only the gems you list > Bulk updating Gem source index for:http://gems.rubyforge.org/ > Successfully installed rake-0.8.1 > Successfully installed activesupport-2.1.0 > Successfully installed activerecord-2.1.0 > Successfully installed actionpack-2.1.0 > Successfully installed actionmailer-2.1.0 > Successfully installed activeresource-2.1.0 > Successfully installed rails-2.1.0 > 7 gems installed > Installing ri documentation for rake-0.8.1... > Installing ri documentation for activesupport-2.1.0... > > RDoc failure in lib/active_support/core_ext/class/removal.rb at or > around line 37 column 19 > > Before reporting this, could you check that the file > you''re documenting compiles cleanly--RDoc is not a > full Ruby parser, and gets confused easily if fed > invalid programs. > > The internal error was: > > Terminated > > # gem install rails > Bulk updating Gem source index for:http://gems.rubyforge.org/ > Killed > > # gem install rails > Bulk updating Gem source index for:http://gems.rubyforge.org/ > Killed > > # gem --debug install rails > Exception `NameError'' at /usr/local/lib/ruby/site_ruby/1.8/rubygems/ > command_manager.rb:133 - uninitialized constant > Gem::Commands::InstallCommand > Exception `Gem::LoadError'' at /usr/local/lib/ruby/site_ruby/1.8/ > rubygems.rb:523 - Could not find RubyGem sources (> 0.0.1) > > Exception `EOFError'' at /usr/local/lib/ruby/1.8/net/protocol.rb:133 - > end of file reached > Exception `EOFError'' at /usr/local/lib/ruby/1.8/net/protocol.rb:120 - > end of file reached > Bulk updating Gem source index for:http://gems.rubyforge.org/ > Killed > > # gem uninstall rails > Successfully uninstalled rails-2.1.0 > Remove executables: > rails > > in addition to the gem? [Yn] y > Removing rails > > # gem install rails > Bulk updating Gem source index for:http://gems.rubyforge.org/ > Killed > > Now every time I try the last command, it fails the same way. Any > suggestions?--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Thanks for the suggestion, but nothing showed up in the log. On Jul 17, 5:06 pm, "khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Is it possible that there is a process running on the server that is > detecting high processor utilization due to the gem install and > killing the gem process automatically? > > Maybe you can run tail -f /var/log/messages in a separate terminal > window and then run the gem install in another window for clues as to > what is causing the gem process to get killed. > > I''m just guessing :) I may be very wrong. > > On Jul 17, 3:59 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > > > I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in my VPS hosting account > > on eApps.com. I''ve tried to install Rails several times, without > > success. I then went through the following sequence:<snip> --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Frederick Cheung
2008-Jul-18 07:22 UTC
Re: Rails install failure on VPS host - suggestions?
If the problem was the documentation then you''re probably ok actually. The --no-rdoc option will stop gem generating the rdoc for the gems. Have you tried running your app? Fred On Jul 17, 10:19 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote:> Thanks for the suggestion, but nothing showed up in the log. > > On Jul 17, 5:06 pm, "khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Is it possible that there is a process running on the server that is > > detecting high processor utilization due to the gem install and > > killing the gem process automatically? > > > Maybe you can run tail -f /var/log/messages in a separate terminal > > window and then run the gem install in another window for clues as to > > what is causing the gem process to get killed. > > > I''m just guessing :) I may be very wrong. > > > On Jul 17, 3:59 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > > > > I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in my VPS hosting account > > > on eApps.com. I''ve tried to install Rails several times, without > > > success. I then went through the following sequence: > > <snip>--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I''m now getting this same problem with any gem update command: root-vd897OOnNMeS5qRBFtzyD+ctO0aYwRK9@public.gmane.org /root: gem update --system Updating RubyGems Bulk updating Gem source index for: http://gems.rubyforge.org/ Killed On Jul 17, 3:19 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote:> Thanks for the suggestion, but nothing showed up in the log. > > On Jul 17, 5:06 pm, "khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Is it possible that there is a process running on the server that is > > detecting high processor utilization due to thegeminstall and > > killing thegemprocess automatically? > > > Maybe you can run tail -f /var/log/messages in a separate terminal > > window and then run thegeminstall in another window for clues as to > > what is causing thegemprocess to getkilled. > > > I''m just guessing :) I may be very wrong. > > > On Jul 17, 3:59 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > > > > I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in myVPShosting account > > > on eApps.com. I''ve tried to install Rails several times, without > > > success. I then went through the following sequence: > > <snip>--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Frederick Cheung
2008-Aug-31 14:11 UTC
Re: Rails install failure on VPS host - suggestions?
On 31 Aug 2008, at 14:56, Steve wrote:> > I''m now getting this same problem with any gem update command: > > root-vd897OOnNMeS5qRBFtzyD+ctO0aYwRK9@public.gmane.org /root: gem update --system > Updating RubyGems > Bulk updating Gem source index for: http://gems.rubyforge.org/ > Killed >What version of rubygems have you got? 1.2 is way better than previous ones, especially on systems with not much RAM. Fred> On Jul 17, 3:19 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: >> Thanks for the suggestion, but nothing showed up in the log. >> >> On Jul 17, 5:06 pm, "khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> >> wrote:> Is it possible that there is a process running on the >> server that is >>> detecting high processor utilization due to thegeminstall and >>> killing thegemprocess automatically? >> >>> Maybe you can run tail -f /var/log/messages in a separate terminal >>> window and then run thegeminstall in another window for clues as to >>> what is causing thegemprocess to getkilled. >> >>> I''m just guessing :) I may be very wrong. >> >>> On Jul 17, 3:59 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: >> >>>> I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in myVPShosting >>>> account >>>> on eApps.com. I''ve tried to install Rails several times, without >>>> success. I then went through the following sequence: >> >> <snip> > > >--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I''m at 1.1.1. After a little more investigation, my /var/log/messages shows my gem is getting killed by the oom_killer because it''s using up all my memory. Can I install rubygems 1.2.0 without using rubygems itself? And will that replace rubygems 1.1.1 or install alongside it? What are the issues concerning that? Thanks for your help. On Sun, Aug 31, 2008 at 8:11 AM, Frederick Cheung < frederick.cheung-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > > On 31 Aug 2008, at 14:56, Steve wrote: > > > > > I''m now getting this same problem with any gem update command: > > > > root-vd897OOnNMeS5qRBFtzyD+ctO0aYwRK9@public.gmane.org /root: gem update --system > > Updating RubyGems > > Bulk updating Gem source index for: http://gems.rubyforge.org/ > > Killed > > > What version of rubygems have you got? 1.2 is way better than previous > ones, especially on systems with not much RAM. > > Fred > > > On Jul 17, 3:19 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > >> Thanks for the suggestion, but nothing showed up in the log. > >> > >> On Jul 17, 5:06 pm, "khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > >> wrote:> Is it possible that there is a process running on the > >> server that is > >>> detecting high processor utilization due to thegeminstall and > >>> killing thegemprocess automatically? > >> > >>> Maybe you can run tail -f /var/log/messages in a separate terminal > >>> window and then run thegeminstall in another window for clues as to > >>> what is causing thegemprocess to getkilled. > >> > >>> I''m just guessing :) I may be very wrong. > >> > >>> On Jul 17, 3:59 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > >> > >>>> I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in myVPShosting > >>>> account > >>>> on eApps.com. I''ve tried to install Rails several times, without > >>>> success. I then went through the following sequence: > >> > >> <snip> > > > > > > > > > >-- Steven Line 303-910-1212 sline00-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I installed the latest rubygems without using rubygems itself and that fixed the out of memory problems. Here''s how to do that: I downloaded rubygems 1.2.0 from www.rubyforge.org and untarred it. I cd''d into the directory and ran ruby setup.rb That installed rubygems 1.2.0 for me. Now everything works fine. Thanks for the help. Steve On Aug 31, 8:59 am, "Steven Line" <slin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I''m at 1.1.1. > > After a little more investigation, my /var/log/messages shows my gem is > getting killed by the oom_killer because it''s using up all my memory. > > Can I install rubygems 1.2.0 without using rubygems itself? And will that > replace rubygems 1.1.1 or install alongside it? What are the issues > concerning that? > > Thanks for your help. > > On Sun, Aug 31, 2008 at 8:11 AM, Frederick Cheung < > > > > frederick.che...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > On 31 Aug 2008, at 14:56, Steve wrote: > > > > I''m now getting this same problem with any gem update command: > > > > r...-vd897OOnNMeS5qRBFtzyD+ctO0aYwRK9@public.gmane.org /root: gem update --system > > > Updating RubyGems > > > Bulk updating Gem source index for:http://gems.rubyforge.org/ > > > Killed > > > What version of rubygems have you got? 1.2 is way better than previous > > ones, especially on systems with not much RAM. > > > Fred > > > > On Jul 17, 3:19 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > > >> Thanks for the suggestion, but nothing showed up in the log. > > > >> On Jul 17, 5:06 pm, "khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > >> wrote:> Is it possible that there is a process running on the > > >> server that is > > >>> detecting high processor utilization due to thegeminstall and > > >>> killing thegemprocess automatically? > > > >>> Maybe you can run tail -f /var/log/messages in a separate terminal > > >>> window and then run thegeminstall in another window for clues as to > > >>> what is causing thegemprocess to getkilled. > > > >>> I''m just guessing :) I may be very wrong. > > > >>> On Jul 17, 3:59 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > > > >>>> I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in myVPShosting > > >>>> account > > >>>> on eApps.com. I''ve tried to install Rails several times, without > > >>>> success. I then went through the following sequence: > > > >> <snip> > > -- > Steven Line > 303-910-1212 > slin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
Steve, If rubygems is getting killed because of compilations using too much CPU (which can peg a CPU), I would get concerned that hosting Rails is going to also prove frustrating obviously depending on the configuration of their(your hosts'') quota processes. Definitely you should look at mod_rails to slim down your memory usage before you go too far down this road. As they might be even more restrictive on memory than CPU. Lastly, get ready to run something in cron to keep an eye on your Rails app and restart if your hosting provider kills off processes sometimes. H On Aug 31, 11:51 am, Steve <slin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I installed the latest rubygems without using rubygems itself and that > fixed the out of memory problems. Here''s how to do that: > > I downloaded rubygems 1.2.0 fromwww.rubyforge.organd untarred it. > I cd''d into the directory and ran ruby setup.rb > That installed rubygems 1.2.0 for me. > > Now everything works fine. > > Thanks for the help. > > Steve > > On Aug 31, 8:59 am, "Steven Line" <slin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > I''m at 1.1.1. > > > After a little more investigation, my /var/log/messages shows my gem is > > getting killed by the oom_killer because it''s using up all my memory. > > > Can I install rubygems 1.2.0 without using rubygems itself? And will that > > replace rubygems 1.1.1 or install alongside it? What are the issues > > concerning that? > > > Thanks for your help. > > > On Sun, Aug 31, 2008 at 8:11 AM, Frederick Cheung < > > > frederick.che...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > On 31 Aug 2008, at 14:56, Steve wrote: > > > > > I''m now getting this same problem with any gem update command: > > > > > r...-vd897OOnNMeS5qRBFtzyD+ctO0aYwRK9@public.gmane.org /root: gem update --system > > > > Updating RubyGems > > > > Bulk updating Gem source index for:http://gems.rubyforge.org/ > > > > Killed > > > > What version of rubygems have you got? 1.2 is way better than previous > > > ones, especially on systems with not much RAM. > > > > Fred > > > > > On Jul 17, 3:19 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > > > >> Thanks for the suggestion, but nothing showed up in the log. > > > > >> On Jul 17, 5:06 pm, "khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <khurr...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> > > > >> wrote:> Is it possible that there is a process running on the > > > >> server that is > > > >>> detecting high processor utilization due to thegeminstall and > > > >>> killing thegemprocess automatically? > > > > >>> Maybe you can run tail -f /var/log/messages in a separate terminal > > > >>> window and then run thegeminstall in another window for clues as to > > > >>> what is causing thegemprocess to getkilled. > > > > >>> I''m just guessing :) I may be very wrong. > > > > >>> On Jul 17, 3:59 pm, wFredk <rubyh...-pmaMCokcf3dZroRs9YW3xA@public.gmane.org> wrote: > > > > >>>> I''ve installed Ruby 1.8.6 and Rubygems 1.1.1 in myVPShosting > > > >>>> account > > > >>>> on eApps.com. I''ve tried to install Rails several times, without > > > >>>> success. I then went through the following sequence: > > > > >> <snip> > > > -- > > Steven Line > > 303-910-1212 > > slin...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org--~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
cheap hosting for students http://javaprovider.net no one can beat them -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---