Date: Wed, 3 Jan 1996 08:07:54 +0100 (MET) From: Andreas Klemm <andreas@knobel.gun.de> To: David Greenman <davidg@Root.COM> Cc: Daniel Leeds <cosmos@sponsor.octet.com>, hackers@freebsd.org Subject: Re: find problems Message-ID: <Pine.BSF.3.91.960103080332.245C-100000@knobel.gun.de> In-Reply-To: <199601021811.KAA00274@corbin.Root.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <<<
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960103080332.245C-100000>