drubin@prism.poly.edu (Dave Rubin) (05/22/91)
We are using AT&T 730X X-Windows terminals running XR4 clients off a Convex C120. The AT&T terminals operate in both standard and X-Windows mode, with a feature to toggle back and forth. The problem is, when the terminals are left in standard mode, the X-Windows server is in a stop mode. Therefore, clients cannot communicate with the server during this time, causing a large number of messages to be queued. Clients (such as xclock and xload) eat up a very large amount of CPU time and memory when trying to communicate with the stopped server. I suspect that the clients are constantly trying to send messages to the server, with no delay between retries. Is there any way, such as an X Server or toolkit option, to limit the client's activity when trying to communicate with a dormant server? Or is there some way to combat this problem on the 730X? Any info would be appreciated ... please respond through E-mail. -- Dave Rubin Polytechnic University drubin@prism.poly.edu