I have, for the first time, installed ruby using rvm.
I run my backups via crontab, calling a bash script that runs a ruby
script. However, that script now tell me that it doesn’t know about
ruby.
So I entered two lines in the bash script:
RVM=/usr/local/rvm/scripts/rvm
test -e $RVM && source $RVM
and it runs OK; but it seems to me that this is not the way it should be
done. Is it?
Cron runs as sh shell. it doesn’t read bashrc or profile.d files like
rvm.sh. so it will not know where to find ruby that’s installed in rvm.
for one of our project this is how we’ve been running things:
Note : We recommend to add cron job for checking the available network
connections. Add following into the crontab :
*/5 * * * * bash -c ‘source /etc/profile.d/rvm.sh&& /usr/bin/env
ruby /usr/local/rvm/gems/ruby-1.9.3-p125/bin/ispunity monitor’
test -e $RVM && source $RVM
Note : We recommend to add cron job for checking the available network
connections. Add following into the crontab :
*/5 * * * * bash -c ‘source /etc/profile.d/rvm.sh && /usr/bin/env ruby
/usr/local/rvm/gems/ruby-1.9.3-p125/bin/ispunity monitor’
That would better, because calling something containing the 1.9.3-p125
would have to be changed with every change of the ruby version.
However, although I suppose I have the newest rvm (1.14.0), I have no
rvm_shell
That would better, because calling something containing the 1.9.3-p125
would have to be changed with every change of the ruby version.
However, although I suppose I have the newest rvm (1.14.0), I have no
rvm_shell
That would better, because calling something containing the 1.9.3-p125
But that gives the following error:
/usr/local/rvm/gems/ruby-1.9.3-p194/gems/ispunity-0.0.4/lib/isp_unity.rb:4:in
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ispunity:19:in load' from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ispunity:19:in ’
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in eval' from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in ’
Hi Wybo,
Thanks for bringing this bug to our notice. We reproduced it on our
system using ruby 1.9.3-p194. although the same code & gem works fine on
ruby 1.9.3-p125. We logging code has been fixed in the source at github,
and will be available in the next release after testing, along with the
new features and other bug fixes currently being implemented.
We request you to follow us on twitter @ispunity so that we can keep you
updated about the next release, and file bug reports on github :
/usr/local/rvm/gems/ruby-1.9.3-p194/gems/ispunity-0.0.4/lib/isp_unity_log.rb:10:in <top (required)>': Log level must be in 0..7 (ArgumentError) from /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:inrequire’
from
/usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in require' from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/ispunity-0.0.4/lib/isp_unity.rb:4:in<top (required)>’
from
/usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in require' from /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:inrequire’
from
/usr/local/rvm/gems/ruby-1.9.3-p194/gems/ispunity-0.0.4/bin/ispunity:4:in <top (required)>' from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ispunity:19:inload’
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ispunity:19:in <main>' from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:ineval’
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in
`’
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.