My coworker and I spent hours finding this fix. Before the fix, we would have Spork running, run Rspec with --drb, and the Rspec would give the "No DRb server running." error. It would then continue to run the specs in both Spork and the local Rspec process.
Allows Rspec to connect to DRb server (Spork)
What OS are you running on? We went back and forth on this a couple of years ago and ended up using localhost because it seemed to work on all OS's whereas 127.0.0.1 would cause intermittent hanging on OS X if you were tied to a network. Disconnect from the network and all was well. This may have been tied to a specific ruby implementation (it was a couple of years back), or perhaps even a spork implementation detail, but never-the-less, I'd need to be convinced that this would work for all users before accepting it.
Strange.. we had the opposite problem. Spork was working on 2 different Ubuntu 10.04 boxes and 1 Laptop with Windows 7 on it. But it was failing on 4 of our iMacs with OSX Snow Leopard on them and 2 Macbook Pros with OSX Lion on them. Once we implemented this patch, it worked for all machines. So we have our project pointed to my branch. One of the iMacs we used was right out of the box with JRuby 1.6.3 freshly installed on it.
Why not make this configurable, somehow?
@c00lryguy - I like the idea of making it configurable. You want to take a crack at that?
No movement here in 8 months. Closing as a part of cleaning up issues; if anyone is seeing this problem and has cycles to make it configurable, feel free to open a new pull request :)