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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Wed, 31 May 2000 09:59:09 -0400 To: "'cygwin AT sourceware DOT cygnus DOT com'" Subject: Re: Bug in 'du' and 'find'? Message-ID: <20000531095909.F20020@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: "'cygwin AT sourceware DOT cygnus DOT com'" References: <03904D7A6D26D411A84600062938BEAE0F0074 AT SERV0109> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <03904D7A6D26D411A84600062938BEAE0F0074@SERV0109>; from Frank.Schmidt@fellesdata.no on Wed, May 31, 2000 at 03:50:49PM +0200 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 AT sourceware DOT cygnus DOT com