[wplug] X respawning too fast?

[Poyner, Brandon]

That's the most logical conclusion.  I bet the error messages are
getting logged in 'dmesg' and at the end of /var/log/messages.  I would
either download the drive checking utility from my manufacturer (usually
a DOS boot floppy) or boot into single user mode and run 'badblocks -svn
/mnt' on the partition to see if the problem is a physical drive error.
No sense wasting your time reinstalling/restoring if it's only going to
happen again.  

Brandon Poyner
Network Engineer II
CCAC - College Office
412-237-3086


-----Original Message-----
From: techmike [mailto:mikeslists at access995.com] 
Sent: Thursday, July 22, 2004 11:20 AM
To: General user list
Subject: RE: [wplug] X respawning too fast?


Well, found more..

which isn't the only thing that is broken..

I just went into /usr/bin and did an ls and out of the corner of my eye
I
saw a few lines flash by input / output error..  

Starting to sound like a failing filesystem?

-Mike

-----Original Message-----
From: "Poyner, Brandon" <bpoyner at ccac.edu>
To: "General user list" <wplug at wplug.org>
Date: Thu, 22 Jul 2004 10:06:51 -0400
Subject: RE: [wplug] X respawning too fast?

> I'd still be looking at why 'which' is failing with an i/o error.  All
> it should be doing is walking your $PATH in order looking in each
> directory for the specified file.  The only thing that comes to mind
is
> either your 'which' has become corrupted or one of the directories in
> unreadable.  Let's say you made /usr/X11R6/bin its own mount point and
> put it on removable media, mount it and then eject the media.  I bet
> 'which' would fail when trying to read that directory with an i/o
> error.
> You could also try reinstalling the which rpm.
> 
> Brandon Poyner
> Network Engineer II
> CCAC - College Office
> 412-237-3086
> 


_______________________________________________
wplug mailing list
wplug at wplug.org
http://www.wplug.org/mailman/listinfo/wplug