> See RH bug 5093, which describes the fix procedure on a dying xfs
> [which is what is being described -- see a tail of
> /var/log/messages after trying to stop and then start xfs].
>
> Quick answer -- something has bunged up the fonts.dir (a
> post-install script has failed, etc.) -- fix i
On Tue, Feb 08, 2000 at 02:07:38PM -0500, R P Herrold wrote:
> On Tue, 8 Feb 2000, Bob Tennent wrote:
>
> > b) permissions on /tmp are wonky.
> >
> > 4 drwxrwxrwt 8 root root 4096 Feb 8 10:39 /tmp/
>
> Actually this is not wonky, it is 'sticky' and proper.
You missed part of th
On Tue, 8 Feb 2000, Bob Tennent wrote:
> b) permissions on /tmp are wonky.
>
> 4 drwxrwxrwt 8 root root 4096 Feb 8 10:39 /tmp/
Actually this is not wonky, it is 'sticky' and proper.
> > Another possibility may be that XF86Config is setup wrong.
> > Needs to match init.d/xfs.
>
I recently had this problem too. The (-1) should be implying
a port number of 65535, which should be OK. I've got two machines
that I recently installed RH 6.1 from the same CD. Both installations
are seemingly identical. However, on one, X fails with exactly your
problem, and is fixed by spec
> From: Hal Burgiss <[EMAIL PROTECTED]>
>
Thanks for the suggestions. I can see the point of not using a
network port. But I still don't see why it doesn't work.
> > The command xfs -port -1 produces the following unenlightening messages:
> >
> > _FontTransSocketINETCreateListener: Unable
On Mon Feb 07 2000 at 16:18, Hal Burgiss wrote:
> On Mon, Feb 07, 2000 at 02:06:03PM -0500, Bob Tennent wrote:
> > I seem to have messed up something and can't figure out what.
> > The command xfs -port -1 produces the following unenlightening messages:
I think you have the wrong syntax there (o
On Mon, Feb 07, 2000 at 02:06:03PM -0500, Bob Tennent wrote:
> I seem to have messed up something and can't figure out what.
> The command xfs -port -1 produces the following unenlightening messages:
>
> _FontTransSocketINETCreateListener: Unable to get service for -1
> _FontTransMakeAllCOTSSer
