[comp.protocols.tcp-ip] SCO's TCP/IP: "out of streams resources"

tkevans@oss670.UUCP (Tim Evans) (04/24/91)

We're running SCO Xenix 2.3.2 with SCO TCP/IP and have been getting
error messages "out of streams resources".  These generally come
when a series of rcp's are executed in a short time--i.e., a 
backup via the network.

Can anyone suggest a workaround, or a fix that might be available?

Thanks.  Please use the address *BELOW* for E-mail replies.
-- 
INTERNET	tkevans%woodb@mimsy.umd.edu
UUCP 		...!{rutgers|ames|uunet}!mimsy!woodb!tkevans
US MAIL		6401 Security Blvd, 2-Q-2 Operations, Baltimore, MD  21235	
PHONE		(301) 965-3286

rpc@hpcndaw.CND.HP.COM (Ron Poppen-Chambers) (04/29/91)

> We're running SCO Xenix 2.3.2 with SCO TCP/IP and have been getting
> error messages "out of streams resources".  These generally come
> when a series of rcp's are executed in a short time--i.e., a 
> backup via the network.
> 
> Can anyone suggest a workaround, or a fix that might be available?
> 

Run the "crash" command. This lets you look at a bunch of system information,
run the "strstat" command under crash. This will tell you the number of times
each size message block has been allocated and has failed an allocation request.
Then edit /etc/conf/cf.d/stune (or run the /etc/conf/cf.d/configure comand)
to up the number of steams message blocks for the size(s) that crash
said failed.

Hope this helps.


-------------------

Ron Poppen-Chambers
rpc@hpcnd.cnd.hp.com

Advice is like most things that are free, you get what you pay for. (me)

keith@spider.co.uk (Keith Mitchell) (05/02/91)

> > We're running SCO Xenix 2.3.2 with SCO TCP/IP and have been getting
> > error messages "out of streams resources".  These generally come
> > when a series of rcp's are executed in a short time--i.e., a
> > backup via the network.
> >
> > Can anyone suggest a workaround, or a fix that might be available?
> >
>
> Run the "crash" command. 

Unfortunately, there is no "crash" command in SCO *Xenix*. It only exists
in SCO Unix. Instead, there is a command in SCO Xenix Streams/TCP called
/usr/bin/sw, which just (dynamically) outputs the stream block usage.
(I don't recall this being documented anywhere).

Once you can see what it is running out of, you can go down the custom
menus and rebuild the kernel with tweaked-up values.

Keith Mitchell                  (postmaster)

Spider Systems Ltd.             Spider Systems Inc.
Stanwell Street                 12 New England Executive Park
Edinburgh, Scotland             Burlington
Phone: +44 31-554 9424          MA 01803
Fax:   +44 31-554 0649          +1 (617) 270-3510

keith@spider.co.uk              keith%spider.co.uk@uunet.uu.net
...!uunet!ukc!spider!keith      zspz01%uk.ac.ed.castle@nsfnet-relay.ac.uk