From: Emil Ong <onge@...>
Date: 2001-07-06T01:48:43+09:00
Subject: [ruby-talk:17331] SIGUSR1/2 ?

Hi,

I'm embedding ruby into an application that already uses SIGUSR1 and
SIGUSR2.  Is there any reason why ruby catches these signals?  Can I
safely modify signal.c so that it doesn't catch them?  If they aren't
really necessary, would it be reasonable to have a function that stopped
ruby from catching them in the C API (e.g. rb_ignore_sigusr())?

Thanks,
Emil