From owner-freebsd-questions Sun Oct 13 23:10:11 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA29766 for questions-outgoing; Sun, 13 Oct 1996 23:10:11 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA29756 for ; Sun, 13 Oct 1996 23:10:09 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.7.5/8.6.12) with SMTP id XAA00377; Sun, 13 Oct 1996 23:10:04 -0700 (PDT) Date: Sun, 13 Oct 1996 23:10:04 -0700 (PDT) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: Sergios cc: questions@freebsd.org Subject: Re: find etc/ In-Reply-To: <2.2.32.19961013210810.009b891c@prometheus.hol.gr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 13 Oct 1996, Sergios wrote: > while we are at "find" can somebody explain me why a find . -name > "something" takes so long and if there is a way I can speed things up.....3 > minutes to find all "somestring" from / and this on a eide system with 64Mb > memory......a filesystem total of 1.2G .... Do you mean find . -name .... or find / -name? find . shoudn't take any time at all, while / should (find has to traverse ALL the directories!). Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major