Thank you for the follow-up and the equivalent to netstat.
(pythonpub)bash-3.2$ lsof -iTCP
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
X11.bin 775 kevinveroneau 0u IPv6 0x04f626d0 0t0 TCP *:6001 (LISTEN)
X11.bin 775 kevinveroneau 1u IPv4 0x04131740 0t0 TCP *:6001 (LISTEN)
X11.bin 775 kevinveroneau 15u IPv4 0x052e8f28 0t0 TCP 192.168.69.1:6001->
192.168.69.100:57200 (ESTABLISHED)
X11.bin 775 kevinveroneau 17u IPv4 0x052e8710 0t0 TCP 192.168.69.1:6001->
192.168.69.100:42179 (ESTABLISHED)
X11.bin 775 kevinveroneau 18u IPv4 0x04131334 0t0 TCP 192.168.69.1:6001->
192.168.69.100:42180 (ESTABLISHED)
X11.bin 775 kevinveroneau 19u IPv4 0x052e8304 0t0 TCP 192.168.69.1:6001->
192.168.69.100:42181 (ESTABLISHED)
X11.bin 775 kevinveroneau 24u IPv4 0x0412faec 0t0 TCP 192.168.69.1:6001->
192.168.69.100:57202 (ESTABLISHED)
X11.bin 775 kevinveroneau 25u IPv4 0x052e7ef8 0t0 TCP 192.168.69.1:6001->
192.168.69.100:57205 (ESTABLISHED)
X11.bin 775 kevinveroneau 26u IPv4 0x0412f2d4 0t0 TCP 192.168.69.1:6001->
192.168.69.100:49611 (ESTABLISHED)
xterm 976 kevinveroneau 1u IPv4 0x04131740 0t0 TCP *:6001 (LISTEN)
iTunes 1100 kevinveroneau 32u IPv4 0x052e9334 0t0 TCP 192.168.0.27:51451->977music.com:http (ESTABLISHED)
Safari 1104 kevinveroneau 17u IPv4 0x054006b0 0t0 TCP 192.168.0.27:51694->iad04s01-in-f19.1e100.net:https (ESTABLISHED)
Safari 1104 kevinveroneau 23u IPv4 0x0513c680 0t0 TCP 192.168.0.27:51547->iad04s01-in-f19.1e100.net:https (ESTABLISHED)
xterm 1196 kevinveroneau 1u IPv4 0x04131740 0t0 TCP *:6001 (LISTEN)
ssh 1227 kevinveroneau 3u IPv4 0x04bd2334 0t0 TCP 192.168.0.27:51377->node1:ssh (ESTABLISHED)
192.168.69.0 is the private subnet which my Xclients connect through. There does not appear to be any indication of display :0 on port 6000 being used. This is from the second launch of X11.org in the same login session. On the remote system I have DISPLAY set to: 192.168.69.1:1.0
In the /tmp directory, there is a folder called launch-xIDsy2 with the socket file of org.x:0
This is rather odd, there is no unix socket for :1... Although that is how I am connecting in this X11.app session.
I also have "Authenticate connections" and "Allow connections from network clients" checked in the Preferences.
To enable the X clients to connect to X11.app, I make use of the xhost command to enable access control from the host and still keeping the server secure.
Perhaps using X11.app in this way is causing this odd side-effect. I am also launching X11.app from the Dock, but am using Snow Leopard, so the past bug with Leopard is resolved(or I'd hope).
Thanks for the help and suggestions so far.
On Wed, Feb 23, 2011 at 7:55 PM, Philip J. Schneider
<email@hidden> wrote:
In normal/default usage, the display number should be "0" at every launch
In general, the program that opens a port should close/unbind it on exit. But, after a process is destroyed by the operating system, its resources *ought* to be harvested, including open ports...hmm...
I'd guess there's still a process with that port open, or something in your workflow is resulting in an unexpected ordering of operations that somehow causes the port to remain in use...
Try running your X11.app and a client, terminate them, and then before trying again, type this at a terminal:
lsof -iTCP
That command will tell you what ports are in use, and by what process name/id.
- Philip
At 4:52 PM -0600 2/23/11, Kevin Veroneau wrote:
Hello,
Firstly, thank you for your last reply to my many questions.
Each time I launch X11.app, if I previously closed it, it increments the display number. This makes it very difficult to automate shell scripts on a remote host to target the X Server on the Mac. I forward the X clients directly through TCP on a private subnet, thus have no use for the encryption and/or compression of SSH forwarding.
On the *NIX machine with the X clients, I place in the .profile file, an export for DISPLAY to equal the IP and display number and screen on my Mac. Since this is a MacBook, I am unable to put it to sleep without first closing X11.app entirely(it just wakes back up if X11.app is running). This makes the automated .profile during a login to connect all my required X clients.
Is this due to a possible memory/port leak in X11.app? How does X11.app allocate a display or check a previous display before binding to the TCP port? After X11.app is closed normally via Command-Q, does it unbind itself from the TCP port correctly? Does X11.app increment display numbers for each successive launch as a security feature?
I am using Mac OS X 10.6.6's X11.app, fully updated.
Thanks.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden