Well, that's simple enough.  I really should stop being lazy and start trying the obvious stuff before asking the list.  Thanks Matz!  ^,^

Sean Etc.
On Tue, May 22, 2001 at 12:31:11AM +0900, Yukihiro Matsumoto wrote:
> Hi,
> 
> In message "[ruby-talk:15474] Ruby catching error signals"
>     on 01/05/21, Sean Middleditch <elanthis / users.sourceforge.net> writes:
> 
> |Is there a way to get Ruby not to catch error signals like sigsegv and such?  I'd prefer to handle everything my way, since there are certain actions that have to be performed on a crash in my app (remove lock files and the like).
> 
> use trap("SEGV"){...} or call signal(2) after Ruby initialization.
> 
> 							matz.