At 03:00 PM 4/24/2001 -0500, you wrote:
>Hm. Guess arbitrarily closing the port was probably a bad idea, huh?
>Is this Linux's/RedHat's fault?
hindsight's 20/20
> > Then, I noticed there was a problem with /usr/bin/slocate. Now,
> > when I say *problem*, I mean the damn thing was chewing up 80%+ of my CPU!
>
>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...
> > 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.
>Assuming (against my better judgment) that all your troubles come from
>slocate, you could check with the maintainers of the slocate package.
> >From the slocate(1) manpage, I read this URL:
>http://www.linux-geek.org/slocate/
dead page. Looked at the home page: strange but unrelated.
>Haven't followed it myself but you might want to start there for docs
>and tips not covered in the manpages, which I'm sure you've read...
>right?
Tried B4 I wrote the list. No man page on my box for slocate. RH6.2
Thanks for any more help you can provide.
BenO
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
