I said:
>> Thanks and apologies; I am lacking in CVS-reading-fu. I shall patch and
report. <<
Wahay! Works lovely. Thanks.
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.
<<
Thanks and apologies; I am lacking in CVS-reading-fu. I shall patch and
report.
>From CVS:
>> Problem seen by Han Boetes and other pe
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,
>> 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.
<<
I've run into this same probl
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.
[snip: patch]
% sudo /usr/libexec/locate.updatedb --se
On Thu, 15 Mar 2007, Otto Moerbeek wrote:
> On Thu, 15 Mar 2007, Han Boetes wrote:
>
> > Otto Moerbeek wrote:
> > > Hmm, can you instrument /usr/libexec/locate.updatedb with a
> > >
> > > tee /tmp/myflist |
> > >
> > > on line 101 to see the filelist it actualy builds?
> >
> > Sure, I ju
On Thu, 15 Mar 2007, Han Boetes wrote:
> Otto Moerbeek wrote:
> > Hmm, can you instrument /usr/libexec/locate.updatedb with a
> >
> > tee /tmp/myflist |
> >
> > on line 101 to see the filelist it actualy builds?
>
> Sure, I just did that and examined /tmp/myflist and it looks
> perfectl
Otto Moerbeek wrote:
> Hmm, can you instrument /usr/libexec/locate.updatedb with a
>
> tee /tmp/myflist |
>
> on line 101 to see the filelist it actualy builds?
Sure, I just did that and examined /tmp/myflist and it looks
perfectly normal.
# Han
On Thu, 15 Mar 2007, Han Boetes wrote:
> Otto Moerbeek wrote:
> > The problem is here that the amount of data is too little to build a
> > complete bigram table. The situation is detected by the diff below.
> >
> > Did you also experience problems when indexing more files?
>
> Yes. It's the same
Otto Moerbeek wrote:
> The problem is here that the amount of data is too little to build a
> complete bigram table. The situation is detected by the diff below.
>
> Did you also experience problems when indexing more files?
Yes. It's the same error as I get with the complete filesystem.
> Index:
On Thu, 15 Mar 2007, Otto Moerbeek wrote:
> On Thu, 15 Mar 2007, Han Boetes wrote:
>
> > Hi,
> >
> > Thanks for your suggestions. Here is what I found. Please let me
> > know if you need more information.
> >
> > This error happens only with the /mnt/mp3 filesystem. Just to make
> > sure it was
On Thu, 15 Mar 2007, Han Boetes wrote:
> Hi,
>
> Thanks for your suggestions. Here is what I found. Please let me
> know if you need more information.
>
> This error happens only with the /mnt/mp3 filesystem. Just to make
> sure it was not a filesystem inconsistency I fsck'ed it. It turned
> out
Marc Balmer wrote:
> Han Boetes wrote:
> > To make debugging that a bit easier I did the following:
> >
> > sudo /usr/libexec/locate.updatedb
> > --searchpath=/mnt/mp3/Klassiek/Schoenberg/PelleasundMelisande
> >
> > which also reproduces the bug.
>
> no wonder it chokes on that terrible music.
Ne
Han Boetes wrote:
Hi,
Thanks for your suggestions. Here is what I found. Please let me
know if you need more information.
This error happens only with the /mnt/mp3 filesystem. Just to make
sure it was not a filesystem inconsistency I fsck'ed it. It turned
out to be fine.
This is what mount ret
Hi,
Thanks for your suggestions. Here is what I found. Please let me
know if you need more information.
This error happens only with the /mnt/mp3 filesystem. Just to make
sure it was not a filesystem inconsistency I fsck'ed it. It turned
out to be fine.
This is what mount returns:
/dev/wd1a on /
On 3/13/07, Han Boetes <[EMAIL PROTECTED]> wrote:
...
As the errormessage suggests there is a character in a filename
somewhere on my filesystem which updatedb doesn't dig.
The cited error message,
"locate database header corrupt, bigram char outside 0, 32-127: 14"
*only* indicates that the
I really don't care what you do. Why do you care what I do?
Paul de Weerd wrote:
> On Wed, Mar 14, 2007 at 03:22:15AM +0100, Han Boetes wrote:
> | Peter Hessler wrote:
> | > I cannot reproduce this bug on -current/macppc. What platform,
> | > and what version of OpenBSD?
> |
> | As the errormess
Bryan Irvine wrote:
> > As the errormessage suggests there is a character in a
> > filename somewhere on my filesystem which updatedb doesn't
> > dig.
> >
> > I just can't find that file.
>
> IIRC there used to be a bug with files that had a % char in the
> name.
Yes I found that report.
> Try us
On Wed, Mar 14, 2007 at 03:22:15AM +0100, Han Boetes wrote:
| Peter Hessler wrote:
| > I cannot reproduce this bug on -current/macppc. What platform,
| > and what version of OpenBSD?
|
| As the errormessage suggests there is a character in a filename
| somewhere on my filesystem which updatedb do
> As the errormessage suggests there is a character in a filename
> somewhere on my filesystem which updatedb doesn't dig.
>
> I just can't find that file.
>
IIRC there used to be a bug with files that had a % char in the name.
Try using find to look for other special chars if that turns up nothi
Peter Hessler wrote:
> I cannot reproduce this bug on -current/macppc. What platform,
> and what version of OpenBSD?
As the errormessage suggests there is a character in a filename
somewhere on my filesystem which updatedb doesn't dig.
I just can't find that file.
# Han
Matthias Kilian wrote:
> On Wed, Mar 14, 2007 at 12:38:52AM +0059, Han Boetes wrote:
> > > This is probably not a bug. You locate database is likely
> > > corrupted, like the error message says.
> >
> > OK, I'll install an alternative locate implementation.
>
> You're just a fucking troll. Go away.
On Wed, Mar 14, 2007 at 12:38:52AM +0059, Han Boetes wrote:
> > This is probably not a bug. You locate database is likely
> > corrupted, like the error message says.
>
> OK, I'll install an alternative locate implementation.
You're just a fucking troll. Go away. I tried my best, I told you
how yo
On Tue, Mar 13, 2007 at 11:07:21PM +0100, Otto Moerbeek wrote:
> > I am discussing a bug which I don't know how to solve. This really
> > belongs in tech@
>
> This is probably not a bug. You locate database is likely corrupted,
> like the error message says.
It could be a bug or a pebkac. I asked
Otto Moerbeek wrote:
> On Tue, 13 Mar 2007, Han Boetes wrote:
> > I am discussing a bug which I don't know how to solve. This
> > really belongs in tech@
>
> This is probably not a bug. You locate database is likely
> corrupted, like the error message says.
OK, I'll install an alternative locate i
ul de Weerd wrote:
:> [moving to misc@, where this sort of problems belong]
:>
:> On Tue, Mar 13, 2007 at 06:42:52PM +0059, Han Boetes wrote:
:> | Hi,
:> |
:> | Since about a week or two I get this problem with locate:
:> |
:> | ~% locate foo
:> | locate database header co
-Otto
>
> Paul de Weerd wrote:
> > [moving to misc@, where this sort of problems belong]
> >
> > On Tue, Mar 13, 2007 at 06:42:52PM +0059, Han Boetes wrote:
> > | Hi,
> > |
> > | Since about a week or two I get this problem with locate:
> > |
&g
o misc@, where this sort of problems belong]
| >
| > On Tue, Mar 13, 2007 at 06:42:52PM +0059, Han Boetes wrote:
| > | Hi,
| > |
| > | Since about a week or two I get this problem with locate:
| > |
| > | ~% locate foo
| > | locate database header corrupt, bigram char outside
t; | Since about a week or two I get this problem with locate:
> |
> | ~% locate foo
> | locate database header corrupt, bigram char outside 0, 32-127: 14
> |
> | Any suggestions on how I can debug this problem?
>
> Have you already tried removing the database and rebui
[moving to misc@, where this sort of problems belong]
On Tue, Mar 13, 2007 at 06:42:52PM +0059, Han Boetes wrote:
| Hi,
|
| Since about a week or two I get this problem with locate:
|
| ~% locate foo
| locate database header corrupt, bigram char outside 0, 32-127: 14
|
| Any suggestions on how
30 matches
Mail list logo
