From: Eric Schwartz Date: 2004-08-14T08:06:06+09:00 Subject: Re: timeouts with threads and SIGALRM Lennon Day-Reynolds writes: > Is the long-running method calling out into C code? Even something > like a socket operation? If so, that system code may be blocking > signals before they can percolate up to the Ruby layer I would try > sending signals from outside the Ruby process to see if they can > interrupt it during the long method. I'm way ahead of you. :) I've tried it with a fork() instead of a new thread, and I've even sent signals from a completely separate shell process. No dice. I'm 99% sure it's the Ruby interpreter's fault, because although I know that multiple SIGALRMs can be condensed into one, I've never heard of only one taking over 30 seconds to be sent to the process it's intended for. -=Eric -- Come to think of it, there are already a million monkeys on a million typewriters, and Usenet is NOTHING like Shakespeare. -- Blair Houghton.