Re: Ruby is eating my signals!

> -----Original Message-----
> From: Eric Schwartz [mailto:[e-mail]] 
> Sent: Tuesday, August 31, 2004 12:17 PM
> To: [e-mail]
> Subject: Re: Ruby is eating my signals!
> 
> 
> I don't mean to be pushy, but this is causing me some fairly 
> sizable pain at the moment; does anyone have an idea as to 
> how I can fix my extension (or alternatively, how to force 
> Ruby to deliver a signal it's currently deferring)?
> 
> Thanks,
> 
> -=Eric

Hi Eric,

Well, one thing I'm curious about is why you need to setup a separate
ALRM handler in addition to a timeout.  I would think wrapping your STAF
query in a timeout, and catching a TimeoutError, would be sufficient.
Please correct me if I'm wrong.

Also, I don't see anything in your source to indicate that you've tried
to trap the ALRM signal anywhere.  Do you have a code snippet you could
share?  That would help.  I'm afraid I don't use STAF so I can't really
test.

Lastly, as a sanity check, create a simple alarm handler and make sure
it works properly on your platform (which I'm guessing is Linux, but I
don't remember for sure):

while 1
   puts "PID: " + Process.pid.to_s
   sleep 2
   trap("SIGALRM"){
      puts "Caught ALRM signal at: " + Time.now.to_s
      exit
   }
end

Then kill -SIGALRM <pid>

Then try adding in timeout code similar to what you're doing with STAF.
Now, if *that* doesn't work, then there may be a bug in Ruby, or perhaps
there's a Linux specific issue.

HTH.

Dan