Path: utzoo!attcan!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.shell
Subject: Re: Why use find?
Message-ID: <1990Oct08.232838.1097@virtech.uucp>
Date: 8 Oct 90 23:28:38 GMT
References: <1990Oct5.145825.9454@diku.dk> <1990Oct06.011438.8265@virtech.uucp> <1990Oct7.001518.14216@diku.dk> <106928@convex.convex.com>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Organization: Virtual Technologies Inc., Sterling VA
Lines: 28

In article <106928@convex.convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>In article <1990Oct7.001518.14216@diku.dk> kimcm@diku.dk (Kim Christian Madsen) writes:
>>cpcahil@virtech.uucp (Conor P. Cahill) writes:
>>Maybe not on your system, but on my system (a SYSV) system, find perfoms
>>a getpwd(3C) each time it enters a directory, and getpwd(3) is by
>>standard implemented by forking a shell to do a pwd(1) in oorder to
>>get the result ... This makes it slow.

Hey, I didn't say that (carefull with those inclusions).

>What an idiotic way to implement that function.  It's also 

Getcwd() works that way on most system V systems.  Since it should be 
a rarely used function (normally only once per execution) it really 
shouldn't matter.  It has been this was at least since PWB Unix (in 
the AT&T family line).

>stupid of whoever sent out such a hopelessly slow version 
>of find without optimizing that.  Bitch at your vendor.

Very true.  Most finds will only run a pwd at start up time (so it knows
where it was started from so it can start any -execs there) not each
time it enters a new directory.

-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170