From: "Guansong Zhang" <guansong@hotmail.com>
To: <cygwin@sourceware.cygnus.com>
Subject: Re: Bug in 'du' and 'find'?
Date: Wed, 31 May 2000 07:28:00 -0000 [thread overview]
Message-ID: <20000531142748.12782.qmail@hotmail.com> (raw)
In-Reply-To: <20000531095909.F20020@cygnus.com>
I have this problem too. But I am on windows 2000. I am not sure if that is
the problem. (With cygwin.dll as 1.1.1)
Basically, the "find" will complain "No such file or directory", while I do
"ls -l", there is d flag there, I mean it is recognized as a directory by
"ls". I don't know why. Hope this may help.
Best regards,
Guansong
----- Original Message -----
From: Chris Faylor <cgf@cygnus.com>
To: <cygwin@sourceware.cygnus.com>
Sent: Wednesday, May 31, 2000 9:59 AM
Subject: Re: Bug in 'du' and 'find'?
> On Wed, May 31, 2000 at 03:50:49PM +0200, Schmidt Frank wrote:
> >Is there something wrong with the way Cygwin traverses directories? Both
> >with the 'du' and 'find' command the traversal prematurely ends in
> >directories with no files -- only containing subdirectories. I get a
message
> >'No such file or directory' in such directories (similar to Linux), but
the
> >commands do not scan these subdirectories. Is there some option I have
not
> >set correctly? I am using Cygwin 1.1.0.
>
> I can't duplicate this problem with the current Cygwin snapshot. I
> don't know if that means this is fixed or if your description is not
> adequate to duplicate the problem.
>
> cgf
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-05-31 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-31 6:52 Schmidt Frank
2000-05-31 6:59 ` Chris Faylor
2000-05-31 7:28 ` Guansong Zhang [this message]
2000-05-31 7:30 ` Chris Faylor
2000-05-31 11:25 ` Jason Tishler
2000-05-31 13:08 ` Chris Faylor
2000-05-31 13:52 Earnie Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000531142748.12782.qmail@hotmail.com \
--to=guansong@hotmail.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).