On Sun, 26 Oct 2008 13:54:54 -0700, Craig White wrote:
[...]
What should I do first??
from command line, cut down your large log files by locating them...
# find /var/log -type f -size +2000k -exec ls -lh {} ; | awk '{ print $8 ": " $5 }'
Proofreading for the third time, I discovered a missing space; now I get no error messages, and it tells me the culprit is /var/log/ messages for yesterday -- with 54GB all by itself. The poor thing must've been going bonkers; gawdknows why ...
and any file that is really large (i.e. /var/log/Xorg.0.log)
command line empty it... # > /var/log/Xorg.0.log
Is there some way to find out what makes that message file so big -- i.e., why the machine was losing its mind? I can't hope to read 54 gigs in my lifetime ...