X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Message-ID: <f60fe000811240942i337f339fm7ae0392f45a13f77@mail.gmail.com>
Date: Mon, 24 Nov 2008 12:42:29 -0500
From: "Mark J. Reed" <markjreed@gmail.com>
To: cygwin@cygwin.com
Subject: Re: find . -regex '.*js' -type f -exec md5sum '{}' \\; really slow!
Cc: "=?UTF-8?Q?J=C3=B6rg_Schaible?=" <Joerg.Schaible@scalaris.com>
In-Reply-To: <1227542941.7201.55.camel@LxPC35>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1227540449.7201.45.camel@LxPC35> 	 <F0D7281DAB048B438E8F5EC4ECEFBDDC0337DE68@esmail.elsag.de> 	 <1227542582.7201.51.camel@LxPC35> <1227542941.7201.55.camel@LxPC35>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Mon, Nov 24, 2008 at 11:09 AM, Bartolomeo Nicolotti wrote:
>
> Hi,
>
> but the command
>
> find . -type f  | xargs md5sum
>
> has problems with blanks in the name of the files:

This isn't a general help list for UNIX tools; they work the same on
Cygwin as on UNIX.  I recommend you search for tutorials online;
http://www.softpanorama.org/Tools/Find/find_mini_tutorial.shtml looks
like it might be helpful for find.

The solution to your problem is the -print0 option to find, coupled
with the -0 option to xargs.

find . -type f -print0 | xargs -0 md5sum

--
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/

