Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 11 Jul 2001 00:43:35 +0200 From: Corinna Vinschen To: cygwin Subject: Re: Error in access() with long file names Message-ID: <20010711004335.C8578@cygbert.vinschen.de> Mail-Followup-To: cygwin References: <3B4B6398 DOT B524F174 AT mvista DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010710122511 DOT 02362e48 AT pop3 DOT cris DOT com> <3B4B6398 DOT B524F174 AT mvista DOT com> <20010710225812 DOT Z8578 AT cygbert DOT vinschen DOT de> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20010710151436 DOT 02adfa10 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.1.0.14.2.20010710151436.02adfa10@pop3.cris.com>; from rrschulz@cris.com on Tue, Jul 10, 2001 at 03:16:31PM -0700 On Tue, Jul 10, 2001 at 03:16:31PM -0700, Randall R Schulz wrote: > Corinna, > > The question remains, shouldn't the response from the access() call > indicate that the named file is not readble (or accessible in any way), > since in fact it is not? You're right. I'm using the latest developers snapshot and the result is /home/corinna[103]$ ./y aaaaaaaaaabbbbbbbbbbccccccccccddddddddddeeeeeeeeeeffffffffffgggggggggghhhhhhhhhh iiiiiiiiiijjjjjjjjjjkkkkkkkkkkkllllllllllmmmmmmmmmmnnnnnnnnnnooooooooooppppppppp pqqqqqqqqqqrrrrrrrrrrssssssssssttttttttttuuuuuuuuuuvvvvvvvvvvwwwwwwwwwwxxxxxxxxx xyyyyyyyyyyzzzzzzzzzz01234567890:/ is NOT readable So the problem is solved in the next Cygwin version. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/