Joshua N Pritikin wrote:
>Have you tried simply calling ->stop() on the SIGTSTP signal watcher?
>I believe that will change the handler back to SIG_DFL.
Documentation fix:
--- lib/Event.pod 2002-01-22 08:00:18.0 +
+++ ../Event.pod.new2004-04-21 08:16:00.0 +0100
@@ -4
Joshua N Pritikin wrote:
>Have you tried simply calling ->stop() on the SIGTSTP signal watcher?
>I believe that will change the handler back to SIG_DFL.
Ah, neat. That gives me option 2. Thanks.
-zefram
On Mon, Apr 19, 2004 at 09:18:08PM +0100, Zefram wrote:
> Before I started using Event, I had a couple of signal handlers that,
> as part of their work, locally modified the handling of their signal.
> The interesting case is with SIGTSTP: after doing some application
> cleanup, it would temporaril
I've got a moderately complex program which I'm switching to an event-loop
architecture, using the Event module. I'm doing something slightly
naughty with signal handlers, and I'd like advice on how best to do it
with Event.
Before I started using Event, I had a couple of signal handlers that,
as
