diff options
author | Father Chrysostomos <sprout@cpan.org> | 2011-02-22 12:53:05 -0800 |
---|---|---|
committer | Father Chrysostomos <sprout@cpan.org> | 2011-02-22 17:46:50 -0800 |
commit | dbfe1e81aad2393c90668c6aee3fb9d47133361d (patch) | |
tree | 64381b5cc33f1a6984768a2998e0faac41f5d9cb | |
parent | 09fcee4e4050e683c4608bbadac4c255a63c8ea5 (diff) | |
download | perl-dbfe1e81aad2393c90668c6aee3fb9d47133361d.tar.gz |
Yet another set of perlfunc tweaks
-rw-r--r-- | pod/perlfunc.pod | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 5a0ecbfdea..149c44b6cc 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -1960,14 +1960,14 @@ X<flock> X<lock> X<locking> Calls flock(2), or an emulation of it, on FILEHANDLE. Returns true for success, false on failure. Produces a fatal error if used on a machine that doesn't implement flock(2), fcntl(2) locking, or lockf(3). -C<flock> is Perl's portable file locking interface, although it locks +C<flock> is Perl's portable file-locking interface, although it locks entire files only, not records. Two potentially non-obvious but traditional C<flock> semantics are that it waits indefinitely until the lock is granted, and that its locks -B<merely advisory>. Such discretionary locks are more flexible, but offer -fewer guarantees. This means that programs that do not also use C<flock> -may modify files locked with C<flock>. See L<perlport>, +are B<merely advisory>. Such discretionary locks are more flexible, but +offer fewer guarantees. This means that programs that do not also use +C<flock> may modify files locked with C<flock>. See L<perlport>, your port's specific documentation, or your system-specific local manpages for details. It's best to assume traditional behavior if you're writing portable programs. (But if you're not, you should as always feel perfectly |