Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!caip!princeton!allegra!ulysses!bellcore!whuxcc!lcuxlm!whuxl!houxm!ho95e!wcs
From: wcs@ho95e.UUCP (#Bill_Stewart)
Newsgroups: net.unix
Subject: Re: FSLS - List big files in file system
Message-ID: <899@ho95e.UUCP>
Date: Thu, 25-Sep-86 22:10:50 EDT
Article-I.D.: ho95e.899
Posted: Thu Sep 25 22:10:50 1986
Date-Received: Fri, 26-Sep-86 20:53:04 EDT
References: <573@ih1ap.UUCP> <1620002@hpcnoe.UUCP> <1986@udenva.UUCP>
Reply-To: wcs@ho95e.UUCP (Bill Stewart 1-201-949-0705 ihnp4!ho95c!wcs HO 2G202)
Organization: AT&T Bell Labs, Holmdel NJ
Lines: 19

In article <1986@udenva.UUCP> wedgingt@udenva.UUCP (Will Edgington/Ejeo) writes:
.......<discussion of find ....... -print | xargs foo     vs
	find ..... -exec foo {} \;
........
>  If I remember right, the original discussion was trying to find the huge
>(10 megabyte plus) file that just swallowed your disk.  I doubt there's more
>than one; the first solution above will therefore be *faster* than using xargs
>.....
>  Now, if you're trying to find and remove the thousands of files someone
>created that left your inode table empty ....  But that's never happened on
>any of the systems here, despite the "know-it-all-but-let's-experiment"
>student consultants we have (I know; I started as one :-).

Just by coincidence, my /usr/spool disk ran out of inodes yesterday.  Of the
2000 files that had arrived in the last find -m -2 days, 93% were netnews.....
and it's not the first time.   (Yes, sometime I'll get around to mkfs'ing with
more inodes, but....)
-- 
# Bill Stewart, AT&T Bell Labs 2G-202, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcs