![](https://seccdn.libravatar.org/avatar/a25e43c496c0d388638254f50430d083.jpg?s=120&d=mm&r=g)
On Wednesday, March 15, 2006 @ 2:23 PM, Ken Schneider wrote:
On Wed, 2006-03-15 at 15:17 -0500, Ken Schneider wrote:
On Wed, 2006-03-15 at 14:09 -0600, Darryl Gregorash wrote:
Specs not listed, as I didn't think they were necassary in this
instance.
Boot into the rescue system on the installation CD/DVD and mount the partition on some working directory, say /mnt. All the major log files are in /var/log, and these are likely the ones that have caused the drive to become filled. So cd /mnt/var/log, then ls -l to see what you are facing. (If you have /var on its own partition, then mount that one, and cd /mnt/log). Hopefully there will be enough old logs lying around that you don't need anymore, and can just delete these. If push comes to shove, you can probably delete messages, firewall, and warn as well,
Better bet is to either delete some of the content from these files or if you don't care use
/mnt/var/log/messages The line above is supposed to start with ">" as part of the command line to easily clear out a file without having to delete the file and touch it to re-create it. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Wow! I had tried various permutations of redirect in the past to try to re-init a file (""" > file", etc.). I never thought to just do "> file". Sometimes, things are just too easy. Greg Wallace