Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!silvlis.COM!mdb From: mdb@silvlis.COM (Mark D. Baushke) Newsgroups: comp.windows.x Subject: Re: sun 3/60 "text: table is full" error message? Message-ID: <8808261600.AA17736@amadeus.silvlis.com> Date: 26 Aug 88 16:00:38 GMT References: <1396@wor-mein.UUCP> Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 70 > Date: 25 Aug 88 23:26:09 GMT > From: uunet.uu.net!wor-mein!jim (Jim Chekerylla) > To: xpert@athena.mit.edu > > I am running X11V2 on a monochrome Sun 3/60 with a local disk and 4 MB of > RAM. It is also a file server for one other Sun 3/60 diskless node. > Others are rloging into my machine from some uVAXen. > > When I run too many demo programs, I get the error message "text: table is > full" in my xterm console window and other people's processes (eg. compiles) > get killed. My display continues to work just fine. Does anyone know what > is going on? It seems if I add more RAM (already ordered), that I'm > just pushing the problem off until a heavier load is reached. The short answer is that you need to configure your kernel to have more text segments. The easiest "quick fix" would be to bump your MAXUSERS to 12. Another possibility would be to modify /sys/conf/param.c something like this: *** /sys/conf/param.c-dist Mon Jul 7 21:28:32 1986 --- /sys/conf/param.c Thu Aug 25 16:23:06 1988 *************** *** 50,54 **** int nproc = NPROC; int maxuprc = MAXUPRC; ! int ntext = 24 + MAXUSERS; int ninode = (NPROC + 16 + MAXUSERS) + 64; int ncsize = (NPROC + 16 + MAXUSERS) + 64; --- 50,54 ---- int nproc = NPROC; int maxuprc = MAXUPRC; ! int ntext = 36 + MAXUSERS; int ninode = (NPROC + 16 + MAXUSERS) + 64; int ncsize = (NPROC + 16 + MAXUSERS) + 64; A combination of both increasing MAXUSERS and changing param.c is also a possible solution. At our site, Sun 3/60s with only 4MB are configured with MAXUSERS 12 based on the STDT60 kernel and no changes to param.c. Note: Do not use the GENERIC kernel if you can avoid it. Start with STDT60 as a base if possible. This question has been covered in depth recently in the Sun-Spots Digest mailing list. You might consider reading up on this topic by getting copies of recent issues of the Digest from the sun-spots archives. I seem to recall that v6n101 and v6n111 discussed this problem, but you might want to get an index of v6 and get all appropriate issues. The standard header for issues of Sun-Spots Digest contains the following: > Send contributions to: sun-spots@rice.edu > Send subscription add/delete requests to: sun-spots-request@rice.edu > Bitnet readers can subscribe directly with the CMS command: > TELL LISTSERV AT RICE SUBSCRIBE SUNSPOTS My Full Name > Recent backissues are available via anonymous FTP from "titan.rice.edu". > For volume X, issue Y, "get sun-spots/vXnY". They are also accessible > through the archive server: mail the request "send sun-spots vXnY" to > "archive-server@rice.edu" or mail the word "help" to the same address > for more information. Enjoy! ------------------------------------------------------------------------------ Mark D. Baushke Internet: mdb%silvlis.com@sun.com Silvar-Lisco, Inc. Nameservers: mdb@silvlis.com 1080 Marsh Road Usenet: {pyramid,sun}!silvlis!mdb Menlo Park, CA 94025-1053 Telephone: +1 415 853-6411 / +1 415 969-8328