' > 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 : https://github.com/aruntomar/isp_unity -- Regards, Arun. --------------060907070506050000090707 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 06/04/2012 05:27 PM, Wybo Dekker wrote:

On 2012-06-04 03:43, Florian Gilcher wrote:

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'

also have a look at this

https://rvm.io/integration/cron/

Newer RVMs also have a script called `rvm_shell`.

 $RVM_INSTALL_LOCATION/bin/rvm_shell 1.9.3 -c '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

I am sorry, it is "rvm-shell".

I'm not sure if I'm doing this correctly - I suppose that in the crontab
this is the command to be executed, every 5 minutes (why not once??):

bash -c "source /etc/profile.d/rvm.sh && /usr/local/rvm/bin/rvm-shell
1.9.3 -c 'ispunity monitor'"

But that gives the following error:

/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:in
`require'
	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:in
`require'
	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:in `load'
	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:in
`eval'
	from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in
`<main>'

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 : https://github.com/aruntomar/isp_unity

-- 
Regards,
Arun.

--------------060907070506050000090707--