Re: ooops

[Scott Wood <treii28@xxxxxxxxx>]

--- awilliam@whitemice.org wrote:
> > It's like Adam said: an error log file has likely filled up your
> hard
> > drive.  Use the 'df' comand to see how much of your drive is
> being
> > used.  If you see 100% then you'll need to seek and destroy this
> file.
> > It will likely be in your home directory (/home/$USERNAME).  When
> you
> > boot linux as single you are automatically logged in as root. 
> Just go
> > ahead and cd to /home/$USERNAME ($USERNAME is whatever the name
> of 
> your
> > user account is...) and type 'ls -als'.  This will show you all
> the
> > files in the directory as well as their sizes.  Most error log
> files
> > should be pretty small (DEFINITELY less than 1 MB).  The
> offending 
> file
> > should stick out like a sore thumb.  If the files seem to go by
> to 
> fast
> > you can use SHIFT+PAGE UP to scroll back up the terminal or you
> can 
> use
> > the wonderful pipe: ls -als | less, which will pipe the output
> from ls
> > into a convenient scrolling buffer.

I still think that du or du -s * piped through a sort -nr is more
useful for chasing down huge files.  Of course, if you use just 'du'
you might have to follow that with a 'find' and definately would have
to use a pager to sort through the files/directories.

> 
> It might be a good idea to check in /var/log and /etc/xdm or
> /etc/gdm 
> as well for swollen log files.

going backwards here, I noted he sent a response saying he couldn't
find those directories.  Perhaps it would have been wise to 'splain
what they are just in case.  xdm is an xwindow daemon to handle login
sessions, etc.  manytimes it's error logs will also show up in
something like /usr/X11R6/lib/X11/xdm ...  (try something like 'find
/ -type d -name \*xdm\* -print' )
Brain is going dead on gdm, but isn't the the mouse manager for
console?

Scott

=====

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com