From owner-freebsd-hackers Tue Jan 2 23:28:00 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA19349 for hackers-outgoing; Tue, 2 Jan 1996 23:28:00 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id XAA19339 for ; Tue, 2 Jan 1996 23:27:54 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) id IAA09848; Wed, 3 Jan 1996 08:15:27 +0100 (MET) Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.7.3/8.7.3) with SMTP id IAA01558; Wed, 3 Jan 1996 08:07:55 +0100 (MET) Date: Wed, 3 Jan 1996 08:07:54 +0100 (MET) From: Andreas Klemm To: David Greenman cc: Daniel Leeds , hackers@freebsd.org Subject: Re: find problems In-Reply-To: <199601021811.KAA00274@corbin.Root.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org Precedence: bulk On Tue, 2 Jan 1996, David Greenman wrote: > >when i do this...basically to get a complete listt of all files and dirs > >on a machine, this happens > > > >$ find / > file.output & > > > >it bombs midway through with fts_read no such file or directory? I also watched this error (don't remember exactly if it was using -stable or -current) when doing a ls or du when being in root's home dir. When I removed some of the dot directories (netscape and such) the problem vanished. I couldn't reproduce it :( > Probably because it's going through the files in /proc and this is > obviously very volatile. Using -current is no problem to do a find /proc -print. Next time I'll make a backup of such a directory structure. Andreas /// -- andreas@knobel.gun.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - aklemm@wup.de - \/ ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz apsfilter - magic print filter 4lpd >>> knobel is powered by FreeBSD <<<