🚀 go-pugleaf

In article <2860@bacchus.dec.com>, klee@wsl.dec.com (Ken Lee) writes:
> In article <3002@soleil.oakhill.UUCP>, ephrem@oakhill.UUCP (Ephrem
> Chemaly) writes:
> > Is there any limitations on the number
> > of displays a client can open at one time?
> 
> This is implementation and system dependent.  On many UNIX-type
> systems, X uses sockets for client-server communication.  Each socket
> takes up a file descriptor.  The number of file descriptors is limited,
> very limited on some old systems, though you may be able to increase
> this by reconfiguring your UNIX kernal.
> 

right after the application crashes I ran

$ pstat -T

on the SUN 3/260 to print system statistics.  I got the following:

168/1888 files
151/634 inodes
 51/522 processes
  9/ 88 texts
5920/62088 swap

It seems that I have enough files descriptors left ( I think, since
I am not a UNIX guru).  Is this what you were refereing to ken?
On the other hand right before I got the error on A/UX, pstat gave me:

100 buffers: 0 busy, 0 wanted, 98 done, 1 nodev
82 out of 100 inodes active
35 out of 50 processes active
95 out of 100 files active

It seems that I am getting close to the limits of my system.
After I created another client pstat gave me:

/unix:  no namelist
file: table is full

Here it seems that I am running out of file descriptors. Is this true?
If I try to open yet another client I get from pstat:

/dev/kmem: File table overflow

Here it seems that I am running out of memory.

Are all these conclusion true in the case of A/UX.
How about the SUN?

Thank

Ephrem A. Chemaly        oakhill!soleil!ephrem@cs.utexas.edu
(512)891-2760
MOTOROLA Inc.
6501 W. William Cannon Dr. MS OE28
Austin, TX 78735 U.S.A.