From owner-freebsd-questions Mon Oct 14 01:34:36 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA12494 for questions-outgoing; Mon, 14 Oct 1996 01:34:36 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA12480 for ; Mon, 14 Oct 1996 01:34:24 -0700 (PDT) Received: (from nadav@localhost) by gatekeeper.barcode.co.il (8.7.5/8.6.12) id KAA00355; Mon, 14 Oct 1996 10:32:11 +0200 (IST) Date: Mon, 14 Oct 1996 10:32:11 +0200 (IST) From: Nadav Eiron 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 .... > > ------------------------------------------------------------------------ It takes that long because it works really hard. First, saying "a filesystem" would be inaccurate. Using find from / will search through *all* your file systems (including, for example, /tmp, any NFS filesystems you might have mounted, a cdrom if it's mounted, etc.). generally, if you want it to work faster, be more specific. For example, starting from /usr will make it faster, and will usually get all the files you want. Nadav