On Tue, 24 Apr 2001, Ben Ocean wrote:

>>I do not understand.  logrotate is independent of slocate, it's doubtful
>>that the same issue would cause both of these processes to run haywire,
>>with the exception of filesystem-related problems in /var, maybe.  Did
>>you ever get to the bottom of the logrotate problem?  I don't recall
>>mention of it previously in this thread.
>
>The problem, it appears, was this *interchange* thing I mentioned earlier.
>I finally finished erasing the file. It appears that closing the port
>created innumerable log errors, which in turn were gzipped, and it took an
>hour, AN HOUR of CPU time to erase them. Good grief! Anyway, I now have to
>undo the stupid mistakes I made along the way trying to *fix* the problem.
>Namely the problem of updating slocate that caused it to corrupt the database:
> >>>
>thewebsons:/apache/vhosts# slocate this
>/apache/vhosts/skagitharley/this.html
>fatal error: slocate: decode_db: 'pathlen == -1'! Corrupt Database!
><<<

When you typed "updatedb" and then 10 seconds later killed it,
you corrupted the database.  It harms nothing.  It just means
locate/slocate will not work.  To fix it, run "updatedb &".  Yes
it will use CPU power.  If your machine can't afford to lose CPU
power, no worry, the cronjob runs with priority +19 so it only
runs during idle time.

Make sure /var/ has enough disk space to handle all logfiles,
including rotations, etc.


-- 
Mike A. Harris                  Shipping/mailing address:
OS Systems Engineer             190 Pittsburgh Ave., Sault Ste. Marie,
Red Hat Inc.                    Ontario, Canada, P6C 5B3
http://www.redhat.com           Phone: (705)949-2136




_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to