On Sat, Dec 21, 2013 at 3:27 PM, Jason Tao <jtao / digital-dispatch.com>wrote:

>  On a terminal, try
>
> /usr/bin/evn ruby
>

/usr/bin/env ruby


> echo $?
>
> 127 -- it could not find ruby, check your $PATH or, specify the
> full_path_to_ruby
> 126 -- couldn't start, check with you system administrator to see is there
> any restriction, e.g. SELINUX
>
> J.T
>
>
>
> -----Original Message-----
> From: ruby-talk on behalf of tamouse pontiki
> Sent: Fri 12/20/2013 7:46 PM
> To: ruby-talk ML
> Subject: Re: /usr/bin/env: ruby: No such file or directory
>
> On Fri, Dec 20, 2013 at 4:40 AM, selvag selvag <lists / ruby-forum.com>
> wrote:
>
> > check your shebang line, it should be
> > "#! <path_to_your_ruby VM i.e. /usr/bin/ruby>"
>
>
> Not necessarily. The env is a standard way of invoking ruby with the
> current environment settings intact.
>
> #!/usr/bin/env ruby
>
> should work as is, provided you have ruby installed in a way that your
> environment is aware of. It is the most portable of writing a script header
> in ruby, as it should work across all *nix systems that way.
>
>
> For the OP, I have no idea what opennebula is. If it is some sort of VM or
> VPS thing, you may need to install ruby to begin with, but I have no idea
> what's required to do so.
>
>