kagotani@cs.titech.ac.jp (Hiroto Kagotani) (01/07/90)
I use X with xdmshell, and send abort-display() to xdm terminating it. But R4 xdm does not exit with this message. Here is debug mode log: | ... | ... | dispatching :0 Here, I sent abort-display(). | GreetDone: , (password is 0 long) | UNMANAGE_DISPLAY | select returns -1. Rescan: 0 ChildReady: 1 | signals blocked, mask was 0x0 | Manager wait returns pid: 10910 | Display exited with UNMANAGE_DISPLAY | WaitForSomething | display manager caught SIGUSR1 | select returns -1. Rescan: 0 ChildReady: 0 | WaitForSomething | select returns -1. Rescan: 0 ChildReady: 1 | signals blocked, mask was 0x0 | Manager wait returns pid: 10909 | Zombie server reaped, removing display :0 | WaitForSomething And xdm waiting for something until sending SIGINT. In this time, the server did not exist. | Shutting down entire manager | select returns -1. Rescan: 0 ChildReady: 0 | Nothing left to do, exiting My Xservers file contains only single line, ":0 local /usr/bin/X11/Xsun". Xsun and other clients were compiled with gcc, and running under SUN3OS3.5. Are there anything I have to do yet? Thanks. -- kagotani@cs.titech.ac.jp
keith@EXPO.LCS.MIT.EDU (Keith Packard) (01/08/90)
> I use X with xdmshell, and send abort-display() to xdm terminating it. > But R4 xdm does not exit with this message. Here is debug mode log: R4 xdm now implements XDMCP -- the X Display Manager Control Protocol. This new protocol has xdm waiting for XDMCP requests on UDP port 177, even if there are no local servers to service. You can eliminate this function by setting the udpPort it uses to 0: xdm -xrm 'DisplayManager.requestPort: 0' or, in the xdm-config file place 'DisplayManager.requestPort: 0'. This will make xdm exit when the display is aborted. Keith Packard MIT X Consortium