Re: does PHP5 do locking on PHP files that are included in a way PHP4 didn't?
| From: | Wez Furlong | Date: | Wed, 01 Dec 2004 04:25:18 +0000 |
| Subject: | Re: does PHP5 do locking on PHP files that are included in a way PHP4 didn't? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-13961@lists.php.net to get a copy of this message | ||
It shouldn't be locking the file.
Is there any chance that you have a "zombie" process that does have a
lock? I noticed some weird locking behaviour like this today using a
recent cygwin release (seems like bash held a lock on a directory that
I had cd'ed into earlier in the day). This was totally unrelated to
PHP.
Are you also sure that this isn't the infamous
need-to-sleep(1)-after-unlink-before-creating-a-new-file problem that
has existed on Windows for while?
--Wez.
On Tue, 30 Nov 2004 22:10:01 -0500, Greg Beaver <cellog@php.net> wrote:
> Hi,
>
> I'm running into some race conditions with the CVS of PEAR installer in
> PHP5 where it fails to remove existing php files, and locks a file so
> firmly (Windows XP) that I have to reboot to get the OS to loose its
> grip on it.
>
> I'm wondering if the locking of included source files has changed from
> PHP4, or if I should be looking further into the installer for the problem?
>
> Greg
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>