Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!samsung!uunet!ingr!b11!doyle From: doyle@b11.ingr.com (Doyle Davidson) Newsgroups: comp.windows.x Subject: xhost & close down mode Keywords: xhost Message-ID: <8596@b11.ingr.com> Date: 28 Aug 90 15:19:05 GMT Organization: Intergraph Corp. Huntsville, AL Lines: 42 I was flipping through the MIT - C Language X Interface the other day and while reading the part about server resets (2.6), I noticed that a server reset occurs when the last client closes it's connection and is in close_mode of DestroyAll (default). But it does NOT happen with close_mode of RetainTemporary or RetainPermanent. A common problem that I encounter with novice users of X is their "ignorance" of server resets. A common scenario: X & start server xhost +foobie add machine "foobie" to access list xhost show access list - foobie is not there! Ahh, that good ole server reset strikes again. So I changed xhost to do an: XSetCloseDownMode(dpy, RetainPermanent); right after the XOpenDisplay and it solved my "problem". Now just for academic debate, is there anything wrong with changing the close down mode for xhost? I can't think of any resources that are wasted by this. I know all about XDM and several of the other methods for starting the server so please ignore them for this discussion. As a matter of fact I encourage our users to use XDM. My obligatory: "I'm running on an Intergraph 6040 under X11 R4 with patchlevel 14 and I am standing on one foot, patting my head...." Doyle (SetCloseDownMode(RetainSanity)) Davidson ------------------------------------------------------------------ Doyle C. Davidson | Intergraph Corp. | These comments are... Workstation Graphics Standards | 1 Madison Industrial Park | Huntsville, AL 35806 | (205) 730-2000 | X-clusively my own. | ..!uunet!ingr!doyle | ------------------------------------------------------------------