X-Spam-Check-By: sourceware.org Message-ID: <43D8D4D2.8070302@byu.net> Date: Thu, 26 Jan 2006 06:55:30 -0700 From: Eric Blake User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: Morten Kjarulff CC: cygwin AT cygwin DOT com Subject: Re: rsync: skipping overly long name References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Morten Kjarulff on 1/26/2006 4:20 AM: > I tried to google it, and it seems that the limit is is MAXPATHLEN. It also > seems that MAXPATHLEN is smaller under cygwin than under other systems. > > Is this true? Almost. The name is PATH_MAX, not MAXPATHLEN. > What is the limit? Look in /usr/include/limits.h. 260 (although a few Windows calls are even more restrictive, such as directory names have a max of 248 or so in order to allow an 8.3 filename within the directory). > Is there a way that I can come around it (other than renaming my files ;-)? Not on Windows 9x machines - it is a fundamental limitation of the ASCII Windows system calls. And even on Windows NT machines, it would be a MAJOR patch to cygwin to use the Unicode Windows system calls (where your limit increases to 32k, but it is still a limit); read the list archives, this topic has come up before. - -- Life is short - so eat dessert first! Eric Blake ebb9 AT byu DOT net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFD2NTS84KuGfSFAYARAr+3AKCGgurUGgSqBuzFL42qf/hUT4Dq/wCgwAS0 NgueeH5B+dk8woJOQ1OqFdM= =eL4P -----END PGP SIGNATURE----- -- 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/