Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!agate!ICSI.Berkeley.EDU!stolcke
From: stolcke@ICSI.Berkeley.EDU (Andreas Stolcke)
Newsgroups: comp.windows.x
Subject: xdm shutdown problems
Keywords: xdm, signal, xnews
Message-ID: <1990Oct31.215012.17911@agate.berkeley.edu>
Date: 31 Oct 90 21:50:12 GMT
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Reply-To: stolcke@ICSI.Berkeley.EDU (Andreas Stolcke)
Organization: International Computer Science Institute, Berkeley, CA
Lines: 28

I'm having two problems getting XDM to do what I want:

1. Although the xdm man page clearly says

     When sent a SIGTERM, xdm terminates all sessions in progress
     and exits.  This can be used when shutting down the system.

  SIGTERM seems to shut xdm & server down properly *only* if the 
  "terminateServer" resource is set to true (i.e. the server is restarted
  for every session). If not, xdm will happily continue running after a
  SIGTERM, fire up another server, and the only way to get rid of it is
  to send it a SIGKILL and separate SIGTERM to the server.

  Is this a bug or a feature?  What about fixes?

2. When using xdm to manage Sun's XNeWS server, it seems "terminateServer"
   *has* to be true for sessions to start properly.  you can't just
   leave the server running because it will die as soon as somebody tries
   to start a new session.  I guess XNeWS just isn't compatible enough
   to the MIT server when it comes to xdm-server interaction.  This is a
   pitty since XNeWS takes a long time to start up.

   Any workarounds ?

-- 
Andreas Stolcke
International Computer Science Institute	stolcke@icsi.Berkeley.EDU
1957 Center St., Suite 600, Berkeley, CA 94704	(415) 642-4274 ext. 126