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/
