On Sun, 15 Jul 2007, Steve Fairhead wrote: > >> On Thu, 15 Mar 2007, Otto Moerbeek wrote: > > I see the problem. The problem occurs if top bigrams contain spaces. > These are not handled correctly by awk. We'll have to use a field > separator that can not be in a bigram. A tab is well suited, AFAKS. > > Try this. > <patch snipped> > << > > I've run into this same problem on 4.1 stable, fully patched: > > >> locate database header corrupt, bigram char outside 0, 32-127: 14 << > > It's been there some weeks now; the weekly script completes just fine with > no error messages, and the database exists. Deleting it and running weekly > manually does not change anything. Hardware is fine. > > Did your patch not make it into 4.1, or have I a) run into a different > issue, or b) totally misunderstood the way new releases get built? > > Steve > http://www.fivetrees.com
As cna be easily checed using cvs (http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/locate/locate/mklocatedb.sh) this diff was committed after 4.1 was tagged. -Otto
