Re: problems with latest x version in incoming

[servis@purdue.edu]

*- Rob Browning wrote about "Re: problems with latest x version in incoming"
| Branden Robinson <branden@ecn.purdue.edu> writes:
| 
| > This is a feature, not a bug.  If xdm is installed, the daemon will attempt
| > to start in the postinst, just like any other package that ships a daemon.
| > Before starting, however, xdm uses the parse-xf86config script (in the
| > xserver-common package) to attempt to determine if the XF86Config file is
| > legal.  If it isn't, xdm will not start.
| 
| Has anyone had time to add the "more than Y failed attempts to launch
| X in a 15 second period shuts xdm down" improvement that was discussed
| a while back?
| 

I was one of the ones trying to use the Xreset_0 script to trap the
resets but it did not work as expected, I can't recall why though.

>From what I can tell from xdm's man page this is supposed to be
supported already, but apparently it doesn't seem to work.  I filed a
but report a while ago(#24406: xbase: xdm does not use openDelay, 
openRepeat, openTimeout, startAttempts resources).  I can't imagine
this is a Debian specific problem unless there is some compile time
option to enable/disable these.  I do wish this could be addressed.


>From the xdm's man page:

       DisplayManager.DISPLAY.openDelay

       DisplayManager.DISPLAY.openRepeat

       DisplayManager.DISPLAY.openTimeout

       DisplayManager.DISPLAY.startAttempts
              These numeric resources control the behavior of xdm
              when   attempting  to  open  intransigent  servers.
              openDelay is the length of the pause  (in  seconds)
              between successive attempts, openRepeat is the num­
              ber of attempts to make, openTimeout is the  amount
              of  time to wait while actually attempting the open
              (i.e., the maximum time  spent  in  the  connect(2)
              system  call)  and  startAttempts  is the number of
              times this entire process is done before giving  up
              on the server.  After openRepeat attempts have been
              made, or if openTimeout seconds elapse in any  par­
              ticular  attempt,  xdm  terminates and restarts the
              server, attempting to connect again.  This  process
              is repeated startAttempts times, at which point the
              display is declared dead  and  disabled.   Although
              this  behavior  may  seem  arbitrary,  it  has been
              empirically developed and works quite well on  most
              systems.  The default values are 5 for openDelay, 5
              for openRepeat, 30 for openTimeout and 4 for  star­
              tAttempts.


-- 
Brian 
---------------------------------------------------------------------
"Never criticize anybody until you have walked a mile in their shoes,  
 because by that time you will be a mile away and have their shoes." 
							   - unknown  

Mechanical Engineering                              servis@purdue.edu
Purdue University                   http://www.ecn.purdue.edu/~servis
---------------------------------------------------------------------