On Sat, Sep 22, 2012 at 2:26 PM, Robin McKay [email protected]
I’ve had exactly the same result as MSAN when I tried jruby --ng
You said that you had exactly the same result as Mauro, but I don’t
see the similarity in what you and he were trying to do, since he was
running an executable that itself calls jruby, and you’re running a
Could you post here the exact command you’re using, and the resulting
Without Nailgun jruby myprog.rb works perfectly. (Xubuntu 12.04)
Perhaps someone could explain what adding --ng to JRUBY_OPTS does.
Normally I don’t do anything with that variable and ‘echo $JRUBY_OPTS’
returns a blank line.
Please see the reply I just sent to Mauro for more on this. When you
add --ng to JRUBY_OPTS , JRuby sees that you want to run it in a
Nailgun server, and does so. This is pretty amazing, because you can
be running dozens of tasks in a Nailgun server, and only one JVM is
doing it. You can verify this by running jvisualvm (comes with the
JDK), and noting the JVM’s it finds (displayed on the left side)
(anyone know a way to display all running JVM’s on the command line?).
If you run irb without Nailgun, you’ll see a new JVM there; but if
you run irb with Nailgun, you’ll see that no new JVM shows up.
Does it matter to Nailgun where the JRuby interpreter is located?
No. The JRuby installation includes Nailgun, and when you ask JRuby
to use Nailgun, it knows where to find it.