Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!usc!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!keith
From: keith@EXPO.LCS.MIT.EDU (Keith Packard)
Newsgroups: comp.windows.x
Subject: Re: xdm abort-display() question
Message-ID: <9001071927.AA14745@expo.lcs.mit.edu>
Date: 7 Jan 90 19:27:29 GMT
References: <4168@koudai.cs.titech.ac.jp>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 16


> 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