> 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 to get service for -1
 > > _FontTransMakeAllCOTSServerListeners: failed to create listener for tcp
 > > 
 > > On the other hand, xfs -port 7100 works fine, and I can then do
 > > xset +fp tcp/localhost:7100 as usual.  
 >
 > unix/:-1 creates a socket in the filesystem in /tmp. Likely things to
 > look for are a) filesystem is filled past normal user limits (xfs runs
 > as non-root user) 

/dev/hda7             7.4G  1.7G  5.3G  24% /
/dev/hda1              15M  1.9M   12M  13% /boot
/dev/hda5             1.9G  224M  1.6G  12% /home

b) permissions on /tmp are wonky. 

4 drwxrwxrwt   8 root     root         4096 Feb  8 10:39 /tmp/

   Another
 > possibility may be that XF86Config is setup wrong. Needs to match
 > init.d/xfs.
 >
Shouldn't be relevant;  xfs fails as above before X is started.
And without using init.d/xfs.

Anybody else have a suggestion?

Bob T.

-- 
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null

Reply via email to