Re: The XDM trap

[servis@purdue.edu]

*-Jeff Sheinberg ( 9 Jul)
| Raul Miller writes:
|  > servis@purdue.edu <servis@purdue.edu> wrote:
|  > > You are probably right since this is what is run on the local
|  > > machine.  But if modifying the X wrapper to stop xdm is not possible
|  > > then /etc/X11/xdm/Xreset_0 seems to be the best place.
|  > 
|  > Actually, Xreset_0 is a better place to do it.  X is used by
|  > xinit, but Xreset_0 is only used by xdm.
| 
| If I read the following excerpt from the xdm(1) man page
| correctly:
| 
|        DisplayManager.DISPLAY.openDelay
| 
|        DisplayManager.DISPLAY.openRepeat
| 
|        DisplayManager.DISPLAY.openTimeout
| 
|        DisplayManager.DISPLAY.startAttempts

[description trimmed]

| 
| Is all that needs to be done is just to set the appropriate values
| in the xdm config file.
| 

Hmmm, I just discovered that Xreset_0 is not even run when the Xserver
fails to start, it must only run after a successful session.Oops!

I also tried the above poperties, even though they are stated to be
defaults, in the xdm-config file.  This didn't work either.  It appears
xdm is reading the file but these config options don't seem to
influence it.  I will file a bug on this.

Back to square one.
 
Brian 
-- 
Mechanical Engineering                              servis@purdue.edu
Purdue University                   http://www.ecn.purdue.edu/~servis


--  
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org