search for: unfroz

I found it - there has to be a /var/lib/nfs directory with a few subdirectories under it. Once I had created them all, I could run rpc.statd, and that unfroze everything. Thanks to all, esp. Bill for mentioning rpc - that was the clue for me. mhr

Hi -- I''m upgrading an app from Rails 2.0.2 to 2.3.5 in development on a Mac OS/X Leopard. I unfroze the old Rails files, froze the 2.3.5 gem on the machine into the app, and some quick tests of the app showed no problems. However, after trying to run rake db:migrate, it fails silently. Run with trace I get the output below. I gather it might be related to plugin initialization or load paths,...

...uldn''t have been possible under WDF. *** WARNING *** Just to spell it out clearly, do not use these drivers on a production DomU. And if you use them on a production Dom0, make sure you have good backups. There was a bug that made my Dom0 freeze for 5-10 minutes (no lasting damage when it unfroze though). That bug is fixed now but it''s always possible that there could be others *** WARNING *** Almost everything that was working before should be working now, but obviously this version hasn''t seen nearly as much testing. The one thing that definitely is not working is disa...

...uldn''t have been possible under WDF. *** WARNING *** Just to spell it out clearly, do not use these drivers on a production DomU. And if you use them on a production Dom0, make sure you have good backups. There was a bug that made my Dom0 freeze for 5-10 minutes (no lasting damage when it unfroze though). That bug is fixed now but it''s always possible that there could be others *** WARNING *** Almost everything that was working before should be working now, but obviously this version hasn''t seen nearly as much testing. The one thing that definitely is not working is disa...

Just ran svn up this morning, and got this (after running ./script/ generate rspec) escher: ./script/spec spec/models/item_spec.rb Finished in 8.0e-06 seconds 0 examples, 0 failures ./script/spec:4:in `run'': wrong number of arguments (3 for 1) (ArgumentError) from ./script/spec:4 Using rails 1.2.3, rspec trunk, on Mac OS X.4.9. Any ideas, or is this a bug in

Just sharing an experience with you all -- hopefully you take better precautions than I do. :-) I have a few sites built with Rails 0.8.3 that were ugpraded to 1.0. The newer sites are on edge rails. So when I heard 1.1 had come out, I unfroze my new apps, and installed the new gem for Rails 1.1. The sites that was operating on edge rails worked just fine. However, the sites that were working fine on 1.0 suddenly broke, and started spewing FCGI errors. Of course, I''m lazy and I didn''t check them right away. Serves...