From: Paul Fenwick Date: Tue, 1 Jun 2004 11:31:34 +0000 (+1000) Subject: Re: [PATCH] UPDATE - Grammatical fixes and explanations in perlfunc.pod (sysopen) X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c188b25736dd43fe36b8fadf99d73c80b2374583;p=p5sagit%2Fp5-mst-13.2.git Re: [PATCH] UPDATE - Grammatical fixes and explanations in perlfunc.pod (sysopen) Message-ID: <20040601013134.GA11005@perltraining.com.au> p4raw-id: //depot/perl@22885 --- diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 5ff4cef..b918cac 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -5750,7 +5750,7 @@ using the C<|>-operator. Some of the most common values are C for opening the file in read-only mode, C for opening the file in write-only mode, -and C for opening the file in read-write mode, and. +and C for opening the file in read-write mode. For historical reasons, some values work on almost every system supported by perl: zero means read-only, one means write-only, and two @@ -5767,10 +5767,15 @@ process's current C. In many systems the C flag is available for opening files in exclusive mode. This is B locking: exclusiveness means here that -if the file already exists, sysopen() fails. The C wins -C. - -Sometimes you may want to truncate an already-existing file: C. +if the file already exists, sysopen() fails. C may not work +on network filesystems, and has no effect unless the C flag +is set as well. Setting C prevents the file from +being opened if it is a symbolic link. It does not protect against +symbolic links in the file's path. + +Sometimes you may want to truncate an already-existing file. This +can be done using the C flag. The behavior of +C with C is undefined. You should seldom if ever use C<0644> as argument to C, because that takes away the user's option to have a more permissive umask.