Never mind ... (Was: When running ruby scripts, runsv tightly loops)

[Lloyd Zusman <ljz@asfast.com>]

It turns out that there was a file permissions problem within the runit
directory structure for managing my ruby daemon.  Once I corrected it,
runsv stopped looping.  Therefore, this had nothing to do with the ruby
interpreter.

All is well now.

I'm sorry for the bandwidth.


Lloyd Zusman <ljz@asfast.com> writes:

> I'm successfully using runit for managing a number of daemons.  However,
> I have encountered a problem when the daemon is a ruby script.
>
> It seems like no matter what the script is doing, the runsv process that
> is managing the script seems to be running in a tight loop and taking up
> a high percentage of my cpu.  This even occurs during a do-nothing ruby
> program, such as the following:
>
>   #!/usr/bin/ruby
>   while true
>     sleep(10)
>   end
>
> Assuming that this is called '/usr/local/bin/myscript', the 'run'
> script looks like this:
>
>   #!/bin/sh
>
>   exec 2>&1
>
>   exec /usr/local/bin/myscript
>
>   exit 1
>
> The 'myscript' process itself takes up a miniscule amount of resources;
> only the 'runit' script which is managing it seems to be looping.
>
> Has anyone else run into this problem with ruby scripts and runit?
>
> By the way, I don't see this problem with python or perl scripts.
>
> Could there be something about the ruby interpreter itself which could
> be causing runsv to behave this way?  If so, can anyone suggest a
> fix for this?
>
> Thanks in advance.
>
> -- 
>  Lloyd Zusman
>  ljz@asfast.com
>  God bless you.
>
>

-- 
 Lloyd Zusman
 ljz@asfast.com
 God bless you.