Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!pasteur!dog.ee.lbl.gov!nosc!humu!nctams1!nctams1!pnet16!tomj From: tomj@pnet16.cts.com (Tom Jenkins) Newsgroups: comp.unix.xenix.sco Subject: Re: Xenix-Digiboard Problems Message-ID: <1991May30.145604.601@ncep1.uucp> Date: 30 May 91 14:56:04 GMT Sender: root@ncep1.uucp (Super user) Organization: People-Net [pnet16], NCTAMS EASTPAC Lines: 42 chip@chinacat.unicom.com (Chip Rosenthal) writes: >In article <1991May26.201728.26322@ncep1.uucp> > tomj@pnet16.cts.com (Tom Jenkins) writes: >>The problem is that our Xenix system hangs >>every two-three weeks for no apparent reason. > >I'm not sure why you are blaming the Digiboard. The PC/8e is a >fine card - the one I recommend for 8-port UNIX and XENIX systems. > >I'd suggest that you are running out of clists. If you've got eight >ports activly banging away - ain't no way the distributed configuration >is going to work without hanging. Increase NCLIST and rebuild your >kernel. (I won't repeat the procedure - I summarized it earlier today >in another article.) > >TFM (section 8.7.2) in the administrator's guide suggests 5 to 10 >clists is the average required per terminal. (Don't count just serial >lines - you've got a bunch of multiscreen's too, right?) The max is >16. So, if you've got 8 serial lines and 4 multi screens active, that >means you need 60 to 120 clists average, 192 maximum. SCO distributes >XENIX with NCLIST set to 100. I'd recommend 200 for your configuration. > >Systems do wierd things when you run out of clists - kinda like >what you are describing. > >P.S. It sure would be nice to have a `crash' program for XENIX to >debug these sorts of things. > >-- >Chip Rosenthal | Don't play so >Unicom Systems Development 512-482-8260 | loud, Mr. Collins. Ok, I've changed it to 300. Will let you know if the same thing happens. Btw, thanks for all who responded, and especially Chip and John. --Tom Jenkins UUCP: humu!nctams1!pnet16!tomj ARPA: humu!nctams1!pnet16!tomj@nosc.mil INET: tomj@pnet16.cts.com