Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site sequent.UUCP
Path: utzoo!linus!decvax!tektronix!ogcvax!sequent!merlyn
From: merlyn@sequent.UUCP
Newsgroups: net.unix
Subject: Re: creating pipes in find(1)
Message-ID: <543@sequent.UUCP>
Date: Fri, 28-Sep-84 15:22:10 EDT
Article-I.D.: sequent.543
Posted: Fri Sep 28 15:22:10 1984
Date-Received: Wed, 3-Oct-84 07:14:37 EDT
References: <12378@sri-arpa.UUCP> <50@redwood.UUCP>
Organization: Sequent Computer Systems, Portland
Lines: 30
#endif BUG
rpw3@redwood.UUCP sez:
>> WARNING: Make sure that the "find" is not going to give you so much stuff
>> that your shell (or your system) blows up from an over-large argument list.
>> (That is, DON'T do "for i in `find / -print`")
A way around this is to do something like:
find -print |
while read i
do
<$i commands>
done
Works real slick. Example:
find / -size 0 -print |
while read i
do
ls -ldg $i
done
does an ls on all zero-length files on the system.
-- A particularly personal and original observation from the thought-stream of
Randal L. ("your favorite phrase here") Schwartz, esq. (merlyn@sequent.UUCP)
(Former Official Legendary Sorcerer of the 1984 Summer Olympics)
Sequent Computer Systems, Inc. (503)626-5700 (sequent = 1/quosine)
UUCP: {decwrl,ogcvax,pur-ee,rocks34,shell,unisoft,vax135,verdix}!sequent!merlyn