Now if we take that same simple program and either
don't define $SIG{'TERM'} or set it to 'DEFAULT' we
get END when the parent dies, but when we kill the
child cleanup isn't run (duh) but neither is END. Is
that standard behaviour?
The following is from perlfaq8 (perldoc perlfaq8):
The END
I have a perl script (modified from one of Chris
Nandor's) that I run as a background-process/daemon
via fork(). Now I know I can use kill to end it, but I
was wondering if there was a way that I can catch the
SIGTERM to do one last thing before quitting?
You just need to install a TERM handler
On 18 May 2004, at 19:58, Joseph Alotta wrote:
Greetings,
I am writing a solving function. You pass it the name of a function
and it
calls the functions many times until it finds the value that returns
zero. How would
this be set up?
If you really want to pass the name of the function, then
I need to separate a huge file to small files. It has three columns.
If first column is a number , use this number as a file name (i. e.,
260.dat and 300.dat for following sample), and then writing column 2
and columns 3 to this file.
You didn't say whether you want to preserve anything in the
This is probably not a mac specific perl problem, but I have a web app
that
fires off a perl script which generates a temporary pdf file and then
emails
it to the user. I have been using this syntax:
my $temp_pdf = /tmp/reg_form$$.pdf;
to name the temporary pdf file... Is this a safe way to
whenever I run the simple LWP program below, I get the following error
messages (I am using perl 5.8.0). I get the same message when I try to
build LWP 5.7.2.
[philippe ~/Desktop] % perl testlwp1.pl
dyld: perl Undefined symbols:
_Perl_safefree
[...loads more...]
_perl_get_sv
Trace/BPT trap
