diff options
-rw-r--r-- | pod/perlipc.pod | 2 | ||||
-rw-r--r-- | pod/perlrun.pod | 3 |
2 files changed, 3 insertions, 2 deletions
diff --git a/pod/perlipc.pod b/pod/perlipc.pod index 476fa915fb..48fcb7fc63 100644 --- a/pod/perlipc.pod +++ b/pod/perlipc.pod @@ -35,7 +35,7 @@ and then raise an exception. That's because on most systems, libraries are not re-entrant; particularly, memory allocation and I/O routines are not. That meant that doing nearly I<anything> in your handler could in theory trigger a memory fault and subsequent core -dump - see L<Deferred Signals> below. +dump - see L</Deferred Signals (Safe Signals)> below. The names of the signals are the ones listed out by C<kill -l> on your system, or you can retrieve them from the Config module. Set up an diff --git a/pod/perlrun.pod b/pod/perlrun.pod index 6b01d6c6e7..49573a60a3 100644 --- a/pod/perlrun.pod +++ b/pod/perlrun.pod @@ -1142,7 +1142,8 @@ L<perlvms> and in F<README.vms> in the Perl source distribution. In Perls 5.8.1 and later. If set to C<unsafe> the pre-Perl-5.8.0 signals behaviour (immediate but unsafe) is restored. If set to -C<safe> the safe (or deferred) signals are used. See L<perlipc>. +C<safe> the safe (or deferred) signals are used. +See L<perlipc/"Deferred Signals (Safe signals)">. =item PERL_UNICODE |