From owner-freebsd-current Mon Aug 24 03:40:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04113 for freebsd-current-outgoing; Mon, 24 Aug 1998 03:40:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04107 for ; Mon, 24 Aug 1998 03:40:50 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1/8.9.1) with ESMTP id LAA16853; Mon, 24 Aug 1998 11:39:58 +0100 (BST) Message-ID: <35E142FC.56D506E@tdx.co.uk> Date: Mon, 24 Aug 1998 11:39:56 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: sean@pasebo.nnet.ne.jp CC: current@FreeBSD.ORG Subject: Re: What happened to my 'find' command?? References: <35E13D49.3B9F3FCA@mail.nnet.ne.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Bennett wrote: > last week my 'find' command suddenly went on the fritz; > > find / -name -print > > used to work fine, searching my whole disk for the file in > question. Now however, it immediately prints out a list of 50-60 > lines like the following, yet can't find which I know does exist. > > sean# find / -name httpd -print > *returns* > find: /usr/include/isofs: No such file or directory > find: /usr/include/machine: No such file or directory > find: /usr/include/msdosfs: No such file or directory > find: /usr/include/net: No such file or directory > find: /usr/include/netatalk: No such file or directory > [snip] Just a quick thought - Are you sure your running Find as root, or someone who actually has full permission to go search those directories? Regards, Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message