On 22 March 2013 21:37, Carlos Gottberg <[email protected]> wrote: > Hey, thanks! I was just about to throw the computer through the window. Was > running in a removed directory too.
I expect someone else will do it again in another three or four years. Colin > > > On Friday, 11 September 2009 12:53:51 UTC-4:30, Coby Randquist wrote: >> >> Henry Collingridge wrote: >> > For the record, I had the same problem yesterday. I rebooted my server >> > (a Solaris 10 zone) and that seemed to fix it. >> >> I experienced this issue today, it was caused by the fact that I was >> running in a directory that I had removed from another terminal >> instance. >> -- >> 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 unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-talk/-/mrGqOP9sG2AJ. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
