Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!caip!princeton!allegra!ulysses!mhuxr!mhuxt!houxm!hropus!jrw
From: jrw@hropus.UUCP (Jim Webb)
Newsgroups: net.sources.bugs
Subject: Re: FSLS - List big files in file system - (nf)
Message-ID: <681@hropus.UUCP>
Date: Mon, 15-Sep-86 16:11:03 EDT
Article-I.D.: hropus.681
Posted: Mon Sep 15 16:11:03 1986
Date-Received: Tue, 16-Sep-86 21:31:28 EDT
References: <14600002@siedap.UUCP> <1273@ihlpl.UUCP> <573@ih1ap.UUCP> <1271@jade.BERKELEY.EDU>
Organization: Bell Labs, Holmdel, NJ
Lines: 25

> In article <573@ih1ap.UUCP> sja@ih1ap.UUCP (Steve Alesch) writes:
> >> 
> >> find / -size +nnn -exec ls -l {} \;
> >
> >You can bury the machine this way!!!!  It's incredibly more efficient
> >using xargs(1) instead.
> >
> >	find / -size +nnn -print | xargs ls -l
> >
> >Sorry, but this is one of my pet peeves.
> 
> And for those of you who don't have xargs (I thought such creatures
> died after v6!), you can do:
> 
> 	ls -l `find / +nnn -print`
> 
> Which shell facility is, of course, why I thought xargs-like things
> died after v6...
> 

AAAARRRRGGGGHHHH!!!!  What happens, if, pray tell, the find finds more
that 5120 chars worth of file names????  The shell prints an error about
the arg list too long!   _This_ is why xargs came about...
-- 
Jim Webb             "Out of phase--get help"          ...!ihnp4!hropus!jrw