gnodes & login limits

[George Robbins]

In article <14200 at reed.UUCP> kab at reed.UUCP (Kent Black) writes:
> 
> Problem is building a custom kernel for Shiva.
> 	First build was
> 		maxusers	5	# conserving a little space
> 		physmem		12
> 		no QUOTA
> 
> This new kernel seems just fine except that it refuses to believe our
> upgrade: in fact, it complains "Login limit reached" in the process of
> booting multi-user, after which it allows one login and will not allow
> root to su more than once.  (Nothing, that I know of, remotely like
> this in our BSD4.3 sources.)

The login limit is somehow mediated by the quota code, so no QUOTA,
no multi-user.  This documented in somewhere or other, but it's so
silly you wouldn't really expect it...
>
> Is this related to the gnode count, and if so, how?!?  I have rerun
> install_upgrade (apparently successfully, or so it says).  Is there
> any (other) reason for not increasing the gnode count arbitrarily?
> (Perhaps the nfile count as well, since we ran up against that limit
> in some extreme cases.)
> 
> We do not need more process slots, ports, etc. and with only 8M of
> memory, a few dozen saved bytes does help (well, not much ;-).  No, it
> is not worth the effort for the expected savings (3 minutes of editing
> and compiling and two hours of hair pulling ;-), but my curiosity has
> really gotten the better of me.  Want to know what to expect when I
> try to modify buffer cacheing and the like.

Have fun, the real problem is estimating the real requirements for
some of these resources so that you don't git bit at really bad moment.

-- 
George Robbins - now working for,     uucp:   {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing:   domain: grr at cbmvax.commodore.com
Commodore, Engineering Department     phone:  215-431-9349 (only by moonlite)