Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!lll-lcc!qantel!hplabs!tektronix!tekgen!tektools!jerryp
From: jerryp@tektools.UUCP (Jerry Peek)
Newsgroups: net.sources.bugs
Subject: Re: FSLS - List big files in file system - (nf)
Message-ID: <1559@tektools.UUCP>
Date: Wed, 17-Sep-86 14:36:07 EDT
Article-I.D.: tektools.1559
Posted: Wed Sep 17 14:36:07 1986
Date-Received: Sat, 20-Sep-86 01:34:26 EDT
References: <14600002@siedap.UUCP> <1273@ihlpl.UUCP> <573@ih1ap.UUCP> <1271@jade.BERKELEY.EDU>
Reply-To: jerryp@tektools.UUCP (Jerry Peek)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 24

In article <1271@jade.BERKELEY.EDU> mwm@eris.UUCP (Mike Meyer) writes:
> 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...

[I never used v6...]

The problem here comes when "find" prints so many arguments, and/or such long
pathnames, that "ls" can't handle all of them at once.  "xargs" handles this:
	find / +nnn -print | xargs ls -l
nicely by collecting a certain amount of text, running "ls -l" for that text,
then collecting some more text, doing another "ls -l", etc. until "find" shuts
up.  (It's also possible to specify how much text "xargs" should collect
from "find" in each gulp.)

--Jerry Peek, Tektronix, Inc.
US Mail:    MS 74-900, P.O. Box 500, Beaverton, OR 97077
uucp:       {allegra,decvax,hplabs,ihnp4,ucbvax}!tektronix!tektools!jerryp
CS,ARPAnet: jerryp%tektools@tektronix.csnet
Phone:      +1 503 627-1603