Signals in OpenBSD

deprecated has asked for the wisdom of the Perl Monks concerning the following question:

In linux I find that I can do this:

$SIG{INT}  = &eg; # exit gracefully
$SIG{TERM} = &eg; # in the event we get killed
$SIG{SEGV} = &eg; # ... or worse!
$SIG{CHLD} = &eg; # because we're using system calls
[download]

But I find on my OpenBSD machine that it just runs and quits, no error messages or anything. Is this another stupid mistake on my part, or is there a difference between BSD's signals and GNU's signals?

thanks,
brother dep.

Comment on Signals in OpenBSD Download Code

Replies are listed 'Best First'.
Re: Signals in OpenBSD by merlyn (Sage) on Mar 18, 2001 at 09:26 UTC
Do you really have: `$SIG{INT} = &eg;` [download] as you've written in there? If so, you are running `eg` when you are setting up the assignment. Perhaps you mean either of: `$SIG{INT} = \&eg;` [download] or `$SIG{INT} = '&eg';` [download] Both of which delay the invocation until it's needed.	[reply] [d/l] [select]
Re: Re: Signals in OpenBSD by deprecated (Priest) on Mar 18, 2001 at 20:20 UTC
Yeah, merlyn, goofed when I wrote that here. I wanted to update for everyone. jcwren provided me with this very useful node covering signals in a few operating systems (solaris and FreeBSD). I also dug up this node by tilly which describes the brokenness of signals in perl. In this case I decided to not worry about signals (since this is a BSD-only program, I dont need to worry about signals on linux, which work). You can read perldoc perlipc for more information. brother dep. -- transcending "coolness" is what makes us cool.	[reply]