Re: 2 instances of Xwin
Alexander Gottwald wrote: Amr Mohamed Roushdi wrote: Hi Alex it is me again . I am enclosing the strace fot the 1st instance good and the 2nd instance which blew out . thks for ur help from tracegood 310 2041721 [main] xwin 2284 cygwin_socket: 6 = socket (2, 2, 0) 429 2042150 [main] xwin 2284 cygwin_setsockopt: setsockopt optval=1 323 2042473 [main] xwin 2284 cygwin_setsockopt: 0 = setsockopt (6, 65535, 20 (SO_BROADCAST), 0x22EF84, 4) 672 2043145 [main] xwin 2284 cygwin_bind: 0 = bind (6, 0x769BD0, 16) from trace 304 2658029 [main] xwin 2312 cygwin_socket: 6 = socket (2, 2, 0) 321 2658350 [main] xwin 2312 cygwin_setsockopt: setsockopt optval=1 311 2658661 [main] xwin 2312 cygwin_setsockopt: 0 = setsockopt (6, 65535, 20 (SO_BROADCAST), 0x22EF84, 4) 449 2659110 [main] xwin 2312 __set_winsock_errno: bind:477 - winsock error 10048 - errno 112 306 2659416 [main] xwin 2312 cygwin_bind: -1 = bind (6, 0x769BD0, 16) the winsock error 10048 is WSAEADDRINUSE which means another program is using the port. Up to this bind the logs are nearly identical (only differs in process ids, the :5 vs :10 and some small differences with pointers and handles returned from windows). The logs are about 7 minutes apart. Does it usually work again after 5 - 7 minutes have passed after a failed attempt? bye ago NP: Imperative Reaction - Arrogance the following appeared today in the announcement is it the same as the module suggested thanks again and it works fine with the clipboard amr *** xorg-x11-xwin-gl-6.7.0.0-12 Changes === 2004-07-20 Alexander Gottwald [EMAIL PROTECTED] * xc/programs/Xserver/xdmcp.c (get_addr_by_name): Bugzilla #889: Bind -from address to port number 0 instead of 177 -- Alexander Gottwald
Re: 2 instances of Xwin
I updated my cygwin with the latest dll and it is working fine and -clipboard works as well . thanks again for all the help
Re: 2 instances of Xwin
Amr Mohamed Roushdi wrote: Hi Alex thks againg , I have tried the following after checking that all ports available and nothing is dangling in the /tmp/.X11-UNIX . I tried to fire Xwin withouth the -from parameter I receive a grey screen and no XDM . I am enclosing a TCPVIEW for before the 1st session of xwin and then after starting the 1st Xwin session . It a netstatish output with PID's thks again more interesting is the situation before a failing xwin start. bye ago NP: Diorama - Klarheit -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: 2 instances of Xwin
On Mon, 19 Jul 2004, Amr Mohamed Roushdi wrote: Alex do u need anything more from me . I just tried this myself again. XWin :1 -query server -from host XWin :2 -query server -from host The first works, the second will not startup while the first is running but does when the first is not running. Is this exactly your situation? If it is then there is not much I can do to allow using -from twice without rewriting a large part of the xdmcp part. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: 2 instances of Xwin
On Mon, 19 Jul 2004, Amr Mohamed Roushdi wrote: Alex u are right in diagnosing the problem . Earlier releases accept it though ??? I have no older version handy but found the same code in all releases up to XFree 4.0. I'll check if I find older binaries at home. Now my question would be how to get Xwin running without -from parameter ? I'll take a look at the ls_netdev output you've sent me some time ago and will try to trace which interface is used first and which can be discarded. I am enclosing cygcheck output for the xwin working with 2 sessions . If you use it without -from parameter there must either be a message in the logfile about xdm giving up (sesssion declined error) or some message at the xdm server. You'll have to wait a short time until the timeout happens. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: 2 instances of Xwin
Now my question would be how to get Xwin running without -from parameter ? If you use it without -from parameter there must either be a message in the logfile about xdm giving up (sesssion declined error) or some message at the xdm server. You'll have to wait a short time until the timeout happens. I'm not sure if this applys here, but: i found that my xdm variant here (kdm) has the option SourceAdress. Setting this to true solved my need for -from. [Xdmcp] # Whether KDM should listen to XDMCP requests. Default is true. Enable=true # Use the numeric IP address of the incoming connection instead of the # host name. Use this on multihomed hosts. Default is false SourceAddress=true
Re: 2 instances of Xwin
Amr Mohamed Roushdi wrote: Hi Alex it is me again . I am enclosing the strace fot the 1st instance good and the 2nd instance which blew out . thks for ur help from tracegood 310 2041721 [main] xwin 2284 cygwin_socket: 6 = socket (2, 2, 0) 429 2042150 [main] xwin 2284 cygwin_setsockopt: setsockopt optval=1 323 2042473 [main] xwin 2284 cygwin_setsockopt: 0 = setsockopt (6, 65535, 20 (SO_BROADCAST), 0x22EF84, 4) 672 2043145 [main] xwin 2284 cygwin_bind: 0 = bind (6, 0x769BD0, 16) from trace 304 2658029 [main] xwin 2312 cygwin_socket: 6 = socket (2, 2, 0) 321 2658350 [main] xwin 2312 cygwin_setsockopt: setsockopt optval=1 311 2658661 [main] xwin 2312 cygwin_setsockopt: 0 = setsockopt (6, 65535, 20 (SO_BROADCAST), 0x22EF84, 4) 449 2659110 [main] xwin 2312 __set_winsock_errno: bind:477 - winsock error 10048 - errno 112 306 2659416 [main] xwin 2312 cygwin_bind: -1 = bind (6, 0x769BD0, 16) the winsock error 10048 is WSAEADDRINUSE which means another program is using the port. Up to this bind the logs are nearly identical (only differs in process ids, the :5 vs :10 and some small differences with pointers and handles returned from windows). The logs are about 7 minutes apart. Does it usually work again after 5 - 7 minutes have passed after a failed attempt? bye ago NP: Imperative Reaction - Arrogance -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: 2 instances of Xwin
Amr Mohamed Roushdi wrote: Thanks Alex for ur quick answer . the second never works even with waiting . I will tray and do an strace with the one it works . I don't even know what the actual difference between the two is. The first was started as xwin :10 -query iccpart2 -from icc68651 the second as xwin :5 -query iccpart2 -from icc68651. This is equal except for the display part. But the display has nothing to do with xdmcp. So where is the actual difference. Is it the time? Does XWin called the same way sometimes work and sometimes it does not? Does it work if Xwin is called a second time 5 minutes after it failed first? Another trace will give me no more clue since I'll only see that windows returned an error on bind. It does not include information which process is still using udp port 177. This information can be obtained with netstat I saw you had already sent the output of netstat which contained an entry for udp port 177. But apparently this was taken while XWin was running and is quite useless for finding the program which interferes with XWin. So check with netstat -a if there is an entry UDP icc68651:177 before you start XWin. If there is such an entry try to figure out which program belongs to this entry. bye ago NP: Melotron - Der Anfang -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: 2 instances of Xwin
On Fri, 16 Jul 2004, Alexander Gottwald wrote: Amr Mohamed Roushdi wrote: Hi Alex it is me again . I am enclosing the strace fot the 1st instance good and the 2nd instance which blew out . thks for ur help from tracegood 310 2041721 [main] xwin 2284 cygwin_socket: 6 = socket (2, 2, 0) 429 2042150 [main] xwin 2284 cygwin_setsockopt: setsockopt optval=1 323 2042473 [main] xwin 2284 cygwin_setsockopt: 0 = setsockopt (6, 65535, 20 (SO_BROADCAST), 0x22EF84, 4) 672 2043145 [main] xwin 2284 cygwin_bind: 0 = bind (6, 0x769BD0, 16) from trace 304 2658029 [main] xwin 2312 cygwin_socket: 6 = socket (2, 2, 0) 321 2658350 [main] xwin 2312 cygwin_setsockopt: setsockopt optval=1 311 2658661 [main] xwin 2312 cygwin_setsockopt: 0 = setsockopt (6, 65535, 20 (SO_BROADCAST), 0x22EF84, 4) 449 2659110 [main] xwin 2312 __set_winsock_errno: bind:477 - winsock error 10048 - errno 112 306 2659416 [main] xwin 2312 cygwin_bind: -1 = bind (6, 0x769BD0, 16) the winsock error 10048 is WSAEADDRINUSE which means another program is using the port. Up to this bind the logs are nearly identical (only differs in process ids, the :5 vs :10 and some small differences with pointers and handles returned from windows). Doesn't X bind to different ports depending on the display number? Could it be that the X+10 port is in use, but X+5 isn't? Or am I completely confused? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton
