Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!pacbell.com!ames!sheba.arc.nasa.gov!schoch
From: schoch@trident.arc.nasa.gov (Steve Schoch)
Newsgroups: comp.windows.x
Subject: Re: Behavior of xdm in rel 3 and rel 4 and Xterminals
Keywords: turning Xterms on/off, reloading of Server
Message-ID: <1991Apr25.203926.6991@news.arc.nasa.gov>
Date: 25 Apr 91 20:39:26 GMT
References: <1991Apr22.152633.14240@ap542.uucp>
Sender: usenet@news.arc.nasa.gov (USENET Administration)
Organization: NASA Ames Research Center, Moffett Field, CA
Lines: 24

In article <1991Apr22.152633.14240@ap542.uucp>, mike@ap542.uucp (Mike Hoffmann) writes:
|> Our Xterminals use host-loadable servers. Most of the time it's desirable to
|> turn them off after office hours.
|> 
|> When turning them back on and reloding the server you then got two effects,
|> depending on which release of X you used:
|> 
|> 11.3: xdm kept retrying to find the Xterm to bring up the XLogin screen,
|> this made the xdm-errors file pretty big pretty fast
|> 
|> 11.4: xdm gives up after a while (after reaching it's max # of retries, set
|> in the xdm resources), thus you have to send xdm a SIGHUP from somewhere
|> to get it to re-sync.

The xdm program from X11 R4 uses the XDMCP protocol to find out about X terminals.  NCD supports
XDMCP - I haven't taken a look at other X terminals.

I'll assume you are using NCD X Terminals.   There is a "setup" menu that allows you to specify
a host to which to send the XDMCP messages.  Set that to your "xdm" host and the login window
should come up when you turn the terminals on.

You don't have to put the X Terminal in the Xservers file.  That file can be empty on your host.

	Steve