http://bugzilla.spamassassin.org/show_bug.cgi?id=3828
------- Additional Comments From [EMAIL PROTECTED] 2004-11-15 04:32 -------
Hi,
the patch and the PERL_SIGNALS=unsafe workaround don't work for us, because we
are using Red Hat
Enterprise Linux 3. It comes with perl 5.8.0. The PERL_SIGNALS environment
variable is only honored
for perl >= 5.8.1. According to the perl documentation and my own tests it may
be preferable to set up
the signal handlers differently. Let me quote perlipc:
"Note that some networking library functions like gethostbyname() are known to
have their own
implementations of timeouts which may conflict with your timeouts. If you are
having problems with
such functions, you can try using the POSIX sigaction() function, which
bypasses the Perl safe signals
(note that this means subjecting yourself to possible memory corruption, as
described above). Instead
of setting $SIG{ALRM} try something like the following:
use POSIX;
sigaction SIGALRM, new POSIX::SigAction sub { die "alarm\n" }
or die "Error setting SIGALRM handler: $!\n";
" END OF QUOTE
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
