aboutsummaryrefslogtreecommitdiff
path: root/devel/p5-Perl-Unsafe-Signals/pkg-descr
diff options
context:
space:
mode:
Diffstat (limited to 'devel/p5-Perl-Unsafe-Signals/pkg-descr')
-rw-r--r--devel/p5-Perl-Unsafe-Signals/pkg-descr16
1 files changed, 16 insertions, 0 deletions
diff --git a/devel/p5-Perl-Unsafe-Signals/pkg-descr b/devel/p5-Perl-Unsafe-Signals/pkg-descr
new file mode 100644
index 000000000000..5226f74bc326
--- /dev/null
+++ b/devel/p5-Perl-Unsafe-Signals/pkg-descr
@@ -0,0 +1,16 @@
+In Perl 5.8.0 the so-called "safe signals" were introduced. This means that Perl
+no longer handles signals immediately but instead "between opcodes", when it is
+safe to do so. The earlier immediate handling easily could corrupt the internal
+state of Perl, resulting in mysterious crashes.
+
+It's possible since perl 5.8.1 to globally disable this feature by using the
+PERL_SIGNALS environment variables (as specified in "PERL_SIGNALS" in perlrun);
+but there's no way to disable it locally, for a short period of time. That's
+however something you might want to do, if, for example, your Perl program calls
+a C routine that will potentially run for a long time and for which you want to
+set a timeout.
+
+This module therefore allows you to define UNSAFE_SIGNALS blocks in which
+signals will be handled "unsafely".
+
+WWW: http://search.cpan.org/dist/Perl-Unsafe-Signals/