Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.shell
Subject: Re: Why use find?
Message-ID: <2052@sixhub.UUCP>
Date: 8 Oct 90 23:48:24 GMT
References: <1990Oct5.145825.9454@diku.dk> <1990Oct06.011438.8265@virtech.uucp> <1990Oct7.001518.14216@diku.dk> <106928@convex.convex.com>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 23

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.

  What?? There may be such an implementation somewhere, but I can't
imagine why anyone would do that. Find doesn't need to use an absolute
pathname, it has the starting name on the command line, and if it needed
this info it would only need to do it at most once and keep track of it
from there on.

  Moreover running find on a large directory shows no such info in the
accounting file.

  I guess I'm saying that I doubt that this is (a) needed or (b)
generally true.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me