🚀 go-pugleaf

The context:
We are using emacs 18.55 in an networked environment of
sparc stations,sun-3/60s,and sun-4s. We are running SunOs4.0.3
on a network of about 30 machines using 2 file servers ( sun3 and pyramid)
and 3 swap servers ( 2 sun3s and 1 sun4). All the machines have at least
12 Mbytes and some have 16Mbytes of memory. The machines operate in the X11
environment as well as under SunView.

The symptom:
Occasionally emacs just goes south. This means it is unresponsive for as long as 45 seconds. Banging on control-g sometimes gets it's attention, but not always.
This happens maybe 3 or 4 times a day on a machine with a single user. 
It is most often after some sort of I/O has been  initiated either reading
or writing a file. This happens from vt100s as well as the console.
While I realize that this description is inadequate as a bug report I am 
interested in learning wether or not this is happening to other people.
In particular I would be interested in opinions on this being emacs's
fault,the cursed SunOS4.0's fault, or our own fault.
David DeGeorge
....princeton!idacrd!dld