I think the xfs server was the source of the problem. I did a
service xfs status
and it returned something along the lines of
file pid exists but xfs is dead...
I was about to do a
service xfs stop
followed by
service xfs start
and the service started again just fine. Next, just to make sure I ran
chkconfig xfs on
to make sure that it was in fact starting at boot time.
I then tried to kick off X from an Exceed councel but when I went to the
local terminal it was hung at the gray background and black "X" curser.
I then logged out all the current Exceed users and initiated a
shutdown remotely. The machine shutdown just fine and I repowered the
box and all services as well as X loaded without any problems. I'm all
set now.
Thanks!
-Dan Thomas
>>I pulled this off of the Red hat support forum. I'm having the same
>>problem. Anyone have any idea?
>>Hello,
>>I have the following error when i load : startx
>>---------------------------------------------------------------- Could
>>not init font path element unix/:7100, removing from list!
>>Fatal server error: could not open default font 'fixed'
> This means your font server is not running.
> As root do:
>>service xfs start
> to start it, then try again.
> To make sure xfs gets started on every boot, do as root:
>>chkconfig xfs on
by