From: ts <decoux@...>
Date: 2001-07-06T02:00:11+09:00
Subject: [ruby-talk:17332] Re: SIGUSR1/2 ?

>>>>> "E" == Emil Ong <onge@mcs.anl.gov> writes:

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

 Have you tried to re-install your sighandler after the call to 
 ruby_init() ? 


Guy Decoux