X-Spam-Check-By:	sourceware.org
Message-ID:	<44AE85B7.CB21F832@dessent.net>
Date:	Fri, 07 Jul 2006 09:03:03 -0700
From:	Brian Dessent <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Using du.exe to calculate disk usage on a Microsoft cluster server
References:	<00ec01c6a1dd$ab40c1b0$a501a8c0 AT CAM DOT ARTIMI DOT COM>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Dave Korn wrote:

> filenames.  I *still* don't understand how it is possible for your users to
> create files with names that are longer than the maximum filename length that
> windows permits - this is a limitation of the windows OS and filing system,
> not one that cygwin imposes.

As far as I recall the PATH_MAX of 260 applies to the ANSI versions of
the file APIs, but if you use the Unicode version you can create names
up to 32K UTF-16 characters in length.  So it is entirely possible to
create a file with a name that is too long to access via normal programs
that aren't using the Unicode variants of the API functions (which
includes Cygwin.)

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -