Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!husc6!necntc!ames!oliveb!sun!gorodish!guy
From: guy%gorodish@Sun.COM (Guy Harris)
Newsgroups: comp.unix.questions
Subject: Re: Sun OS obscure error message query - (nf)
Message-ID: <18705@sun.uucp>
Date: Wed, 13-May-87 12:04:08 EDT
Article-I.D.: sun.18705
Posted: Wed May 13 12:04:08 1987
Date-Received: Sat, 16-May-87 04:25:09 EDT
References: <10@citcom.UUCP> <8200007@iaoobelix.UUCP> <752@mcgill-vision.UUCP> <230@dcatla.UUCP>
Sender: news@sun.uucp
Lines: 32

> It seems they either shrank the process table in 3.2 or made it hard
> (I suspect it has to do with the Sys V compatibility stuff).

Well, your suspicions are wrong.  It has nothing whatsoever to do
with the System V compatibility stuff.  The kernel changes for that
were some minor tweaks to some existing system calls, some additional
features in the tty driver, and the System V IPC code (message
queues, semaphores, shared memory) - and that's it.

Furthermore, the size of the process table didn't change in 3.2 - but
then that wouldn't make any difference, since you're *not* running
out of process table slots, but text table slots!  However, the size
of the text table didn't change either.

The size of both the process and text table is set solely in
"param.c", which is distributed as part of every release.  The sizes
of both those tables, as well as several other parameters, are
functions of MAXUSERS; the functions in question did not change
between 3.0 and 3.2.

A bug in earlier releases that caused text table entries to be lost
when the use of an image fetched via NFS was terminated (either by
the process using that image "exec"ing another image or by that
process exiting) if the NFS server in question was down or slow in
responding was fixed in 3.2.  (The code has to get the modes of the
image file, in order to know whether it's a "sticky" image or not; if
the attempt to get the modes failed, as it would do if the server
didn't respond, the code acted as if the image were sticky.)

There may have been another bug introduced into 3.2, but I'd suggest
checking whether you don't just have more different daemons running
on your new system.