On Mon, May 31, 2004 at 09:33:51PM +1000, Paul Fenwick wrote: > --- pod/perlfunc.pod.orig Mon May 31 20:36:19 2004 > +++ pod/perlfunc.pod Mon May 31 21:14:29 2004 > @@ -5672,10 +5672,14 @@ > > In many systems the C<O_EXCL> flag is available for opening files in > exclusive mode. This is B<not> locking: exclusiveness means here that > -if the file already exists, sysopen() fails. The C<O_EXCL> wins > -C<O_TRUNC>. > +if the file already exists, sysopen() fails. C<O_EXCL> may not work > +on network filesystems, and has no effect unless the C<O_CREAT> flag > +is set as well. Setting C<O_CREAT|O_EXCL> prevents symlinks from > +being followed when creating files. Setting C<O_CREAT|O_EXCL> when the path contains a symlink works fine for me. RonaldThread Previous | Thread Next