From: bill@Celestial.COM (Bill Campbell)
Subject: Re: SCO TCPIP >9 LOGINS AGAIN
Organization: Celestial Software, Mercer Island, WA
Date: Tue, 17 Nov 1992 02:00:52 GMT

In <9461.63.uupcb@cccbbs.UUCP> doug.pavey@cccbbs.UUCP (Doug Pavey) writes:

>Well, I read Aris' and Barry's messages about what is involved in
>getting more than 9 tty's to login.  ttyp00 -ttyp08 work fine, ttyp09
>will login, but hang TCP.

Xenix has a max of 32 ptys and SCO UNIX a max around 254.

>How does one debug streams limits problems - determine how many are in
>use, or how many one should set up if the user may be using as many as
>10 processes per login (Progress Database is wonderful).  All users are
>using TCP via 3 8 port Terminal servers. I can get the login messages on
>all ports, until the user actually signs in, we don't seem to have
>problems.  Seems like streams may be the culprit.  How to fix???

You don't say in this post whether you're running Xenix or UNIX
and there are different tools to determine problems with streams
in each.  Xenix comes with a program 'sw', UNIX comes with crash, and
there are some freely distributed monitor programs such as u386mon
available from various ftp sites.

Xenix sw displays:

Pause=1   Calls=74                                Host=camco1

   Resource  Cnt       Use   Total     Max    Fail
     stream: 128        40    4020      53       0
      queue: 256        83    8074     111       0
     mblock:1152        7818508524     636       0
dblk totals:1152        7813966687     543    4469

Mem Size Cnt Med Low   Use   Total     Max    Fail
  1    4 256 230 204     0  893844     155       0
  2   16 128 115 102     2  449445     102     889
  8   32 256 230 204     6 2644776     207    3339
 16   64 256 230 204     5 8602774     147       0
 16  128 128 115 102    50  386387     103      18
 12  256  48  43  38    15  220139      37       0
  4  512   8   7   6     0  102435       7     223
 32 1024  32  28  25     0   50083       8       0
 64 2048  32  28  25     0  584718      13       0
 32 4096   8   7   6     0   32086       5       0
  0 8192   0   0   0     0       0       0       0

Buffers (used/total) = 11/187 Kbytes

This is from a system that has been running for a while now.  Uptime gives:
camco1:ttyp02 /usr/local/bin # uptime
  5:53pm  up 20 days, 55 mins,  12 users,  load average: 1.19, 1.04, 1.02

You would probably want to use crash and it's strstat command on a UNIX
system which gives similar information.  A typical crash display is:
beeson1:ttyp8:/onager/etc > crash
dumpfile = /dev/mem, namelist = /unix, outfile = stdout
> strstat
ITEM                  CONFIG   ALLOC    FREE         TOTAL     MAX    FAIL
streams                  256      158      98           821     171       0
queues                  1280      704     576          2306     786       0
message blocks          2825      309    2516      11357083     705       0
data block totals       2260      309    1950       9675047     669      63
data block size    4     384       51     333         66265     364      63
data block size   16     384        8     376         39861      65       0
data block size   64     512       24     488       4950469      68       0
data block size  128     448      157     290       2974970     392       0
data block size  256     220       33     187        632454     107       0
data block size  512     136       36     100        495575      46       0
data block size 1024      52        0      52         84628      44       0
data block size 2048     104        0     104        430474      25       0
data block size 4096      20        0      20           351      12       0

Count of scheduled queues:   0
>

Bill
-- 
INTERNET:  bill@Celestial.COM   Bill Campbell; Celestial Software
UUCP:   ...!thebes!camco!bill   6641 East Mercer Way
             uunet!camco!bill   Mercer Island, WA 98040; (206) 947-5591
SPEED COSTS MONEY -- HOW FAST DO YOU WANT TO GO?