<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Carsten Haitzler (The Rasterman) wrote: <blockquote cite="mid20070303113758.1c864f66.raster@rasterman.com" type="cite"> <pre wrap="">On Fri, 02 Mar 2007 16:48:23 -0800 John Klingler <a class="moz-txt-link-rfc2396E" href="mailto:john@jupiter.com"><john@jupiter.com></a> babbled: </pre> <blockquote type="cite"> <pre wrap="">Unfortunately, Xlib exits when a display connection is broken. In order to restore an application that has exited when the connection can be re-established, it is necessary to have a parent process without a display connection to detect when the application has exited and restart it. I call this a "heartbeat monitor" and have implemented these on commercial applications. </pre> </blockquote> <pre wrap=""> actuallt that's incorrect. that is only the DEFAULT behavior. you can set an xlib io handler that will stop this from happening and then re-establish the connection. no need for a parent process, shared memory etc. </pre> </blockquote> Really? I was never able to get my io handler to do that. Just how do you go about it? ;-) John </body> </html>