Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:42665
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.157 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=ZhWbtu8k1LPBk6wU2z41E9ROS31YkSDbKMeRkayg+y11NU4/d4LrkJuswA2y5PgpWx
         5V+Dz4DZDCbic/h0R01PFz31Hz37QGywQdb45XOSXFSRjmw52Ixl8xG3J0P3ZyRfmYsL
         X1xRmHPoFV8hp4gynxMk5Fcve72cwQ0f+v+Lw=
MIME-Version: 1.0
In-Reply-To: <C3.3C.27029.393C0794@pb1.pair.com>
References: <E1.9E.27029.AA460794@pb1.pair.com>
	 <fe05d1540901160533n6392fe0eha5ac07dcedddceca@mail.gmail.com>
	 <8C.85.27029.97F90794@pb1.pair.com>
	 <fe05d1540901160803m362e5df2o420e88dd008aea07@mail.gmail.com>
	 <fe05d1540901160812l29fad89dx5cb9b205d7724c0c@mail.gmail.com>
	 <C3.3C.27029.393C0794@pb1.pair.com>
Date: Fri, 16 Jan 2009 18:42:28 +0100
Message-ID: <fe05d1540901160942i7f554647jc80a85721243bba2@mail.gmail.com>
To: Karsten Dambekalns <karsten@typo3.org>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Path length for files on NTFS
From: pierre.php@gmail.com (Pierre Joye)

hi

On Fri, Jan 16, 2009 at 6:27 PM, Karsten Dambekalns <karsten@typo3.org> wrote:

> Oe example with 229 characters:
> /Users/karsten/Sites/typo3v5/Data/Temporary/6e7991cd3e3f10e110df4a26825c1f8c/_www/Cache/Testing/Tags/%CLASS%F3_Widget_Persistence_MessageQueuePersistenceAspect/FLOW3_Reflection-F3_Widget_Persistence_MessageQueuePersistenceAspect
>
> For deeper nested namespaces this will get longer, add some deeper directory
> structure at the start and - bang.

With such naming, you are likely to hit this issue anyway, no matter
the OS. Think about one having his host directories in deeper level,
for example, or the hostnames use some lengthy values/names?

> Now, I never ran into problems with paths being too long for anything I
> tried on Linux or Mac, so what limits exist? Admittedly I never thought
> about that much. Given we live in a world of terabytes I'd expect names to
> be virtually as long as I want. :)

It is system dependent and there is many values.

>> Btw, what do you do when the path len of the path where the cache is
>> stored is closed from MAXPATHLEN (PHP_MAXPATHLEN in userland)? Given
>> than MAXPATHLEN can be between 260 and 2048 (~), that' can happen
>> easily.
>
> Never heard of that constant, thanks for pointing it out. The documentation
> doesn't explain it, is there some background information available
> somewhere?

it reflects the internal constant MAXPATHLEN, which is defined at
compile time (per os/system).

> So, in the best case we hit the roof at ~2k? Good to know...

Keep in mind that the _complete_ path has to fit in there, not only
the last part (your cache name). I think you should rethink a bit the
naming of your caching system, that'll save you some troubles soon
later.

About the 260 limit on windows, we may find an efficitent solution to
increase it in a safe way, but I don't have one at hand right now. I
have to think more about that and see what can be done for 5.3 (which
supports XP+ only, which means NTFS in the most cases).


Cheers,
-- 
Pierre

http://blog.thepimp.net | http://www.libgd.org