Please sign in to comment.
- Loading branch information...
Showing with 31 additions and 1 deletion.
|@@ -125,6 +125,30 @@ processes. For applications with large heaps the gain can be|
|significant. To include `posix-spawn`, simply add it to your `Gemfile` or,|
|if you don't use bundler, install the gem.|
|+Cocaine will attempt to choose from among 3 different ways of running commands.|
|+The simplest is using backticks, and is the default in 1.8. In Ruby 1.9, it|
|+will attempt to use `Process.spawn`. And, as mentioned above, if the|
|+`posix-spawn` gem is installed, it will attempt to use that. If for some reason|
|+one of the `.spawn` runners don't work for you, you can override them manually|
|+by setting a new runner, like so:|
|+Cocaine::CommandLine.runner = Cocaine::BackticksRunner.new|
|+And if you really want to, you can define your own Runner, though I can't|
|+imagine why you would.|
|+### JRuby Caveat|
|+If you get `Error::ECHILD` errors and are using JRuby, there is a very good|
|+chance that the error is actually in JRuby. This was brought to our attention|
|+in https://github.com/thoughtbot/cocaine/issues/24 and probably fixed in|
|+http://jira.codehaus.org/browse/JRUBY-6162. You *will* want to use the|
|+`BackticksRunner` if you are unable to update JRuby.|
|*Security* concerns must be privately emailed to|