[comp.windows.news] Display lock broken

sevans@Eng.Sun.COM (Steve Evans) (06/27/90)

> I am plagued by messages, usually when loading large files into the
> server:

These messages comes from the SunWindows kernel driver.  They are
generated when the NeWS or xnews server doesn't release the SunWindows
display lock within a given number of process virtual seconds (2 is the
default).  If you don't run any SunView programs under NeWS you
shouldn't see them.  However, once you run any SunView programs under
NeWS you may continue to see them even if there are no longer any
SunView programs running.

In the "SunView System Programmer's Guide" in the chapter entitled
"Workstations" in the section entitled "Kernel Tuning Options" you
will see a kernel variable named ws_lock_limit that may be changed
to modify the 2 second default.  The following would permanently
modify the setting to be 8 seconds.

	% su
	# adb -w /vmunix /dev/kmem
	ws_lock_limit?W 8
	ws_lock_limit/W 8
	^D

The main drawback of doing this is that the kernel will deal less
swiftly with display lock hogs.

sevans

jdn@europa.Eng.Sun.COM (Jeff Nisewanger) (06/28/90)

In article <6111@helios.TAMU.EDU> skdutta@cs.tamu.edu (Saumen K Dutta) writes:
>
>>I am plagued by messages, usually when loading large files into the
>>server:
>>
>>Jun 22 14:46:56 apricot Window display lock broken after time limit exceeded
>>by pid 1213
>>Jun 22 14:46:56 apricot You may see display garbage because of this action
>>
>>
>>The only garbage I ever see is the message itself, on my console.
>>
>>Is there a way to disable this feature?
>
>Sometime back this problem had been addressed in this group. I 
>don't remember who answered it but it was like:
>
>%psh
>executive
>Wlecome to X11/NeWS ........
>statusdict begin
>jobtimeout ==
>15
>60 jobtimeout
>jobtimeout ==
>60
>quit
>psh: NeWS server disconnected
>--
>     _                                   ||Internet: skdutta@cssun.tamu.edu  
>    (   /_     _ /   --/-/- _            ||Bitnet : skd8107@tamvenus.bitnet 
>   __)_/(_____(_/_(_/_(_(__(_/_______    ||Uucp : uunet!cssun.tamu.edu!skdutta
>                                 ..      ||Yellnet: (409) 846-8803


	Different problem. The "display lock" stuff is caused by the
SunView compatibility support in the server. SunView has the concept
of a display lock during which only one process can draw into the
screen's framebuffer. Processes are supposed to get the display lock
and then draw something and then release it. Occasionally the server
holds the lock too long and the kernel emits the above warning message.
This isn't a big deal, but it's annoying to get the messages. There
is a way to patch the kernel to increase the default display lock timeout
but I don't know off hand what it is.


	Jeff
--
Jeff Nisewanger                         ARPA: jdn@Eng.Sun.COM
Window Systems Group                    UUCP: ...!sun!jdn
Sun Microsystems, Inc.                  415/336-5743