X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org MIME-Version: 1.0 Date: Fri, 27 Apr 2012 10:28:51 -0400 Message-ID: Subject: find.exe vs. cmd.exe dir command vs. filesystem object in vbs script From: Cary Lewis To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 I have a system that makes use of a number of directories which contain hundreds of thousands of files. I know this is a bad design. I inherited it. The sheer number of files in the directories makes it very difficult to do simple things using cygwin. For example the find command takes a very long time to start outputting filenames. However, in a cmd.exe window, the dir.exe command immediately starts outputting files. I would like to find out which api calls the CMD dir.exe command is using vs. the cygwin find.exe program. In the end I want to build an efficient delete files utility based on date, type, etc. I also need to compare files in the filesystem with references in a database I am starting to think that I should use the CMD dir.exe command and by parsing its output, take appropriate action. Performance is further hampered by the files residing on a SAN. Any thoughts / suggestions? Thanks. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple