Wednesday, April 25, 2001, 11:15:38 AM, Mike Harris wrote:
> On Tue, 24 Apr 2001, Ben Ocean wrote:
>>>All the time? Or just at certain times?
>>
>>Dunno for the slocate problem. When the problem was in logrotate.status
>>(presumably before it got to slocate) it ran for *hours* then crashed.
>>Makes newbies skittish...
> The slocate/locate command searches for files on your hard disk
> by looking them up in a database created nightly at 4:05am by
> a cron job running "updatedb". This job will take a while
> depending on how large your disk is.
And depending on how fast your HDD is and depending on how fast
the contoller is, and depending on how fast your CPU is, and...
>>> > So I d'l'd a new rpm for slocate and
>>> > updated it. Now I get this error when I try to slocate something:
>>> > >>>
>>> > fatal error: slocate: decode_db: 'pathlen == -1'! Corrupt Database!
>>> > <<<
>>>
>>>Since updating slocate, have you run updatedb(1L)?
>>
>>You mean updatedb without the (1L) I presume? It chokes. Gave it about 10
>>seconds then killed the command.
Is there any HDD activity ? There should be, and a lot too :)
tip: updatedb==slocate -u
--
If Bill Gates had a dime for everytime a Windows box crashed...
...,Oh wait, he already does.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
