[NBLUG/talk] Cannot get XWindows to start

[HarryH]

Mark,
The restart of xfs "FAILED".  The chmod 1777 was done ok.  I restored the
/tmp to all the files it had in the first place before the RHN download,
minus a large Coyote Linux file so as to give 16MB more space.  Still no X
on either a reboot or startx command.  Where else should I look to make
changes?

Thanks for the help,
Harry

----- Original Message ----- 
From: "Mark Street" <jet at sonic.net>
To: <talk at nblug.org>
Sent: Friday, January 02, 2004 4:25 PM
Subject: Re: [NBLUG/talk] Cannot get XWindows to start


> The move of /tmp was probably what got you.  /tmp must be set with
specific
> permissions.  The font server cannot place its socket file into /tmp
>
> chmod 1777 /tmp
>
> Then restart your font server.
>
> service xfs restart
>
> You may need some additional filesystem maintenance....  but that should
get
> you back your X.
>
>
> On Thursday 01 January 2004 22:52, HarryH wrote:
> > Hi,
> > The other day, I downloaded from Red Hat Network the latest kernel
version
> > for my RH 7.2 system.  It wanted 23MB on my "/" root file system
> > (/dev/hda5) that was not there.  I moved /tmp and /sbin to another
> > filesystem to create the space.  I downloaded the kernel OK and it said
> > "############# 100% complete" but stalled on "sh: /sbin/grubby" not
found.
> > Obviously, it was in another file system.  I restored the /tmp and /sbin
> > and tried to reboot to see if I got the new kernel.  The old kernel was
> > still there and working as the new one was not successfully installed.
The
> > XWindows (Gnome/KDE) did not come up.  I noticed the "/" file system was
> > 100% full even though it had some space.  I removed the /tmp files to
> > another file system and that freed up 12MB on "/", but df -h still says
it
> > is at 100% capacity.  I tried to do a "startx"  and it gave me the
> > following:
> >
> >   Could not init font patch element unix/:7100, removing from list!
> >   Fatal server error:
> >   could not open default font 'fixed'
> >  XIO: fatal IO error 104 (connection reset by peer) on X Server ":0.0"
> > after 0 requests (0 known processed) with 0 events remaining
> >
> > I did a echo $DISPLAY and it was empty.
> >
> > I am wondering if the 100% full means it cannot/will not use the "/"
file
> > system and therefore not XWindows boot?  It seems to ignore the 12MB
space.
> >
> > I have just installed a second HD and can move some directories to it to
> > give "/" more space?  Also, how do I run the /sbin/grubby as it will not
> > let me "execute a binary file"
>
> -- 
> Mark Street, D.C.
> Red Hat Certified Engineer
> Cert# 807302251406074
> --
> Key fingerprint = 3949 39E4 6317 7C3C 023E  2B1F 6FB3 06E7 D109 56C0
> GPG key http://www.streetchiro.com/pubkey.asc
>
> _______________________________________________
> talk mailing list
> talk at nblug.org
> http://nblug.org/mailman/listinfo/talk
>