Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!vitsun.UUCP!pat From: pat@vitsun.UUCP (Patrick Turley) Newsgroups: comp.windows.news Subject: Broken display lock Message-ID: <8808022253.AA13019@vitsun.com> Date: 3 Aug 88 03:08:17 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 28 In article <2126@ssc-vax.UUCP> dmg@ssc-vax.UUCP (David Geary) writes: >"Window display lock broken because process xxxx blocked" In SunView, processes obtain locks from the windowing system before they write to the screen. These locks time out after 1 second of virtual process time (I think that's right - check the SunView manual if the precise number interests you). If the lock is broken, that is the message you get. I don't have NeWS here so I don't know a lot about it but it seems logical to infer from what I've heard that it is going through the usual SunView arbitration mechanisms (NeWS will run in a SunView window, won't it?) but taking too long on something. I was once interested in increasing the timeout value and called up Sun software support to find out if it was a system parameter that I could fiddle with in some configuration file or something. It turns out that it doesn't appear in a any configuration file but you can increase it by poking a particular location in the kernel. Of course, that means the new value is only good until the system goes down. Perhaps this could be automated by feeding adb's stdin with a script in rc.local. Pat +-------------------------+---------------------------------------+ | | | * * | Patrick Turley | | | | | * * * * | Senior Software Engineer | | | | | * * * * * * | Visual Information Technologies | | | | | * * * * * * | 3460 Lotus Drive | | | | | * * * * | Plano, TX 75075 | | | | * * | (214) 596-5600 convex!vitsun!pat | +-------------------------+---------------------------------------+