X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 11 Jan 2009 10:16:38 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: find assert Message-ID: <20090111091638.GH400@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <495A4B87 DOT 3080009 AT partners DOT org> <20081230170638 DOT GB5230 AT ednor DOT casa DOT cgf DOT cx> <20081230174104 DOT GD5230 AT ednor DOT casa DOT cgf DOT cx> <20081230175246 DOT GE5230 AT ednor DOT casa DOT cgf DOT cx> <20081230190603 DOT GA13443 AT ednor DOT casa DOT cgf DOT cx> <49695A74 DOT 1010302 AT byu DOT net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49695A74.1010302@byu.net> User-Agent: Mutt/1.5.17 (2007-11-01) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jan 10 19:33, Eric Blake wrote: > According to Christopher Faylor on 12/30/2008 12:06 PM: > > This is apparently caused by a symlink that looks like this: > > > > lrwxrwxrwx 1 cgf None 6 Jul 9 2005 n -> //none > > > > I don't remember creating that symlink. Apparently I was checking on > > creating symlinks to nonexistent domains back in 2005. > > > > I don't know if this is a find bug or a cygwin bug. I could see it > > being either or both. > > To some degree, it is a cygwin bug, when "n" points to "//nowhere". If > stat("n",&st) were to fail with the standardized ENOENT, rather than the > cygwin-specific ENOSHARE, then fts_read would have set fts_info to > FTS_SLNONE (a dangling symlink) rather than FTS_NS (stat failed, possibly > from ELOOP). Are you proposing that Cygwin should change setting errno from ENOSHARE to ENOENT? ENOSHARE is only set in one single instance and is only explicitly requested in another. AFAICS, dropping ENOSHARE entirely would only simplify the code and should have no negative consequences (knock on wood here). Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/