summaryrefslogtreecommitdiff
path: root/vms
diff options
context:
space:
mode:
authorJarkko Hietaniemi <Jarkko.Hietaniemi@cc.hut.fi>1997-04-20 22:38:13 +0300
committerChip Salzenberg <chip@atlantic.net>1997-04-23 00:00:00 +1200
commit10a676f83f541430b63a3192b246bf6f86d3b189 (patch)
tree68d8c166d31c1a205281b8088f8e69dfb45bedb3 /vms
parentc1b0f331869f7723157d603165e544a78c1a6206 (diff)
downloadperl-10a676f83f541430b63a3192b246bf6f86d3b189.tar.gz
Two doublewords less
private-msgid: 199704201938.WAA07722@alpha.hut.fi
Diffstat (limited to 'vms')
-rw-r--r--vms/perlvms.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/vms/perlvms.pod b/vms/perlvms.pod
index 830ff613d5..5f9e91f635 100644
--- a/vms/perlvms.pod
+++ b/vms/perlvms.pod
@@ -508,7 +508,7 @@ true, a warning message is printed, and C<undef> is returned.
In most cases, C<kill> kill is implemented via the CRTL's C<kill()>
function, so it will behave according to that function's
documentation. If you send a SIGKILL, however, the $DELPRC system
-service is is called directly. This insures that the target
+service is called directly. This insures that the target
process is actually deleted, if at all possible. (The CRTL's C<kill()>
function is presently implemented via $FORCEX, which is ignored by
supervisor-mode images like DCL.)