summaryrefslogtreecommitdiff
path: root/lib/filetest.pm
diff options
context:
space:
mode:
authorHugo van der Sanden <hv@crypt.org>2002-10-22 15:47:21 +0000
committerhv <hv@crypt.org>2002-10-22 15:47:21 +0000
commit9b488eb89e353c3569ec0fe5076be8c2a5f47436 (patch)
treebf5ae6bdf34912d7fd01ca04440d897d3b7ca7cc /lib/filetest.pm
parent51947a20dc2d93fe0888ee6d69de8ae4aca4aef4 (diff)
downloadperl-9b488eb89e353c3569ec0fe5076be8c2a5f47436.tar.gz
improve 'atomicity' wording
p4raw-id: //depot/perl@18045
Diffstat (limited to 'lib/filetest.pm')
-rw-r--r--lib/filetest.pm3
1 files changed, 2 insertions, 1 deletions
diff --git a/lib/filetest.pm b/lib/filetest.pm
index 21252f35a6..7eb58a68b1 100644
--- a/lib/filetest.pm
+++ b/lib/filetest.pm
@@ -38,7 +38,8 @@ B<NOTE>: using the file tests for security purposes is a lost cause
from the start: there is a window open for race conditions (who is to
say that the permissions will not change between the test and the real
operation?). Therefore if you are serious about security, just try
-the real operation and test for its success. Think atomicity.
+the real operation and test for its success - think in terms of atomic
+operations.
=head2 subpragma access