From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: locate.exe
Date:	11 Apr 2001 12:13:46 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	22
Message-ID:	<9b1hpq$le$1@nets3.rz.RWTH-Aachen.DE>
References:	<3AD3CA93 DOT 4DA31C76 AT lps DOT u-psud DOT fr>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 986991226 686 137.226.32.75 (11 Apr 2001 12:13:46 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	11 Apr 2001 12:13:46 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Daniel Taupin <taupin AT lps DOT u-psud DOT fr> wrote:
>  Finally, I find out thet locate.exe works perfectly... when the
> database is not too big. In fact, when I run

> updatedb c:/     (where c: is a 34 Gigabyte disk with a lot of files)

> then locate crashes with a page fault. But, when I run updatedb on a
> limited number of files, it runs OK. I shall look whether I'm able to
> correct that.

From reading the gnu.utils.bug newsgroup, I seem to remember a bug in
locate having been noticed by others, too. It occurs with certain very
long paths, i.e. it's not the total size of the locatedb, but rather the
length of a single full pathname contained in it. To check, try

	locate "*"

this output all files in the locatedb. It should crash right at the offending
file, then.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -