Re: [SLE] X Server listening on loopback

From: Jeffrey L. Taylor (suse_at_austinblues.dyndns.org)
Date: 01/30/05

  • Next message: Hylton Conacher (ZR1HPC): "Re: [SLE] Problem with SuSE 9.2 and SATA" 
    Date: Sun, 30 Jan 2005 11:28:59 -0600
To: suse-linux-e@suse.com

    Quoting Jorge F?bregas <fabregasj@prtc.net>:
    > Hello everyone,
    >
    > I modified the following file:
    >
    > /etc/opt/kde3/share/config/kdm/Xservers
    >
    > so that my X server won't listen to tcp connetions. I added the "-nolisten
    > tcp" to the main line there. I restarted the X Server and when I use
    > netstat I don' t longer see any line listening on port 6000. Before I had:
    >
    > 0.0.0.0:6000
    >
    > After the change I was expecting to see:
    >
    > 127.0.0.1:6000
    >
    > The problem is I don't see anything now. How come? I thought that the
    > "-nolisten tcp" argument meant that X should listen only on the loopback
    > device. Isn't X client-server model? Or does it use IPC ?
    >

    It is listening on a Unix domain socket, e.g., /tmp/.X11-unix/X0.

    HTH,
      Jeffrey 

    -- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com
  • Next message: Hylton Conacher (ZR1HPC): "Re: [SLE] Problem with SuSE 9.2 and SATA"

    Relevant Pages

    • Re: detecting a closed TCP connection
      ... I don?t have a great deal of experience with TCP so this is just and idea, which I think will work as I have done something similar, under Linux. ... I ran the example Simple Data Server and Client VI?s from the Example finder. ... The second netstat was after I stop the client which in turn kills the server. ... You can see that the netstat commands show the ESTABLISHED status on Port 2055 so this could be your test. ...
      (comp.lang.labview)
    • Re: Internal TCP/IP send buffer?
      ... and that has to be decided at your proxy server. ... UDP or a separate TCP connection to the target and periodically ... connections) constitutes a completely different source of latency. ...
      (microsoft.public.win32.programmer.networks)
    • Re: Netzwerkproblem GBit -> 100MBit
      ... GBit-Kette - flow control zwingend notwendig sei. ... zwischen Client und Server. ... Das kann TCP an der Stelle nicht mehr leisten. ...
      (de.comp.sys.novell)
    • Re: RWW Unavailable
      ... SharePoint 444 TCP ... RWW 4125 TCP ... what did you use for your Web Server Certificate? ... This would really look like a router fault if I didn't have the same ...
      (microsoft.public.windows.server.sbs)
    • Re: Log Out Issues
      ... UDP is the way to go for internet games. ... Apparently the extra overhead in TCP can cause a lot more lag in your game, ... >> Lets say the client sends a log out request to the server reliably. ...
      (microsoft.public.win32.programmer.networks)