Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:17554
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Sat, 6 Aug 2005 01:01:53 +0400
To: Rob Richards <rrichards@ctindustries.net>
Cc: internals@lists.php.net
Message-ID: <20050806010153.15db58be.antony@zend.com>
In-Reply-To: <42F3D095.8010604@ctindustries.net>
References: <42F3D095.8010604@ctindustries.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Questions on stream
From: antony@zend.com (Antony Dovgal)

On Fri, 05 Aug 2005 16:48:21 -0400
Rob Richards <rrichards@ctindustries.net> wrote:

> I was wondering if the following are bugs or expected behavior/wont change.
> 
> Take the following code:
> <?php
> $handle = fopen("file.txt", "w");
> fwrite($handle, "SOME DATA");
> unlink("file.txt");
> if (fwrite($handle, "SOMEMORE") === FALSE) {
>    print "CANNOT WRITE";
> } else {
>    print "Wrote Data";
> }
> fclose($handle);
> ?>
> 
> Under linux the file is deleted and the result is Wrote Data (even 
> though the last fwrite didnt do anything).

That's because on Linux data gets phisically deleted only when number of 
hardlinks to it and number of open descriptors becomes 0.

It's perfectly fine to open & delete file and continue writing to/reading from it.
That's, btw, one of the well known methods used do get a temporary FD. 

> Under windows, the unlink() call results in a permissions denied error.

Yup =) Also on Windows you can't open a file already opened by someone.

> Shouldn't linux not allow the file to be deleted with an open stream as 
> well?

No, why? 

-- 
Wbr, 
Antony Dovgal