"Craig A. Berry" <[EMAIL PROTECTED]> wrote on 01/17/2005 11:55:12 PM:
<snip />
> If I can figure out what the unixes are doing and if it's something
> we can do without causing other problems, I may yet solve this. But
> I may not, and almost certainly won't get to it quickly. So I'm
> afraid you are stuck with one workaround or another for now.
"Stuck?" It works. I'm not complaining.
> BTW, a better workaround than setting PERL_SIGNALS in your
> environment would be to replace your kill sub with the following,
> which I came across in the documentation while digging into this:
> use POSIX;
> sigaction SIGALRM, new POSIX::SigAction sub {
> kill KILL => $pid;
> }
It works. It's magic. I'm using it as of now. Thank you very much. If I
could read, I'd be dangerous.
Results for other operating systems (so far):
Cygwin (Perl 5.8.6): works fine.
MSWin32 (ActivePerl 811 = Perl 5.8.6): "Your vendor has not defined POSIX
macro SIGALRM".
Tom Wyant
This communication is for use by the intended recipient and contains
information that may be privileged, confidential or copyrighted under
applicable law. If you are not the intended recipient, you are hereby
formally notified that any use, copying or distribution of this e-mail,
in whole or in part, is strictly prohibited. Please notify the sender
by return e-mail and delete this e-mail from your system. Unless
explicitly and conspicuously designated as "E-Contract Intended",
this e-mail does not constitute a contract offer, a contract amendment,
or an acceptance of a contract offer. This e-mail does not constitute
a consent to the use of sender's contact information for direct marketing
purposes or for transfers of data to third parties.
Francais Deutsch Italiano Espanol Portugues Japanese Chinese Korean
http://www.DuPont.com/corp/email_disclaimer.html
