SUMMARY: SysV NINODE equivalent??

From: mwp.michael (MWP.MICHAEL@MELPN1.Prime.COM)
Date: Fri Mar 26 1993 - 08:59:00 CST

I queried how to increase the equivalent to the NINODE parameter and the
consensus is that upping MAXUSERS will do the trick (yet another example of
the amazing skill required to tune a Sun!!).

When I looked for NINODE in the config files of course I used an upper-case
search...wrong!! Too much SystemV has addled my brain, 'cause these
parameters are lower case, and "ninode" is defined in at least 1 file:

It is an integer set to:
       ninode = (NPROC + 16 + MAXUSERS) + 64 + 12 * MAXUSERS

Suggestions for the new size for MAXUSERS ranged from "crank it up" to 225 on
a SS10.

If you are looking for SunOS tuning papers, try ( in
the /systems/sun/papers/perfpapers directory. They are all there in
compressed PostScript form.

Thanks for these responses:

-- *** *** *** -- *** *** *** -- *** *** *** --

From: stern@sunne.East.Sun.COM (Hal Stern - NE Area Systems Engineer)

this is all covered in the sunos tuning paper; both NFILE and NINODE
are controlled by maxusers in sunos 4.1.3.

crank it up -- a lot of other caches also depend on it.


-- *** *** *** -- *** *** *** -- *** *** *** --

From: "Jim Davis" <>

I don't think there's a separate parameter for this in 4.1.3. There
is MAXUSERS, which is a general 'scale' knob -- if you increase the
value of MAXUSERS, then a number of kernel tables get bigger. So if
you run out of open files on your system, try increasing the MAXUSERS
value and rebuild your kernel.

Note that if you use the generic kernel Sun typically ships, MAXUSERS
may be quite low to begin with, perhaps as low as 4 or 8. A more
reasonable value for a production system would be 32 or 64. On
several heavily-used SS10s, I turned it up to 225 or so.

-- *** *** *** -- *** *** *** -- *** *** *** --

From: (Michael Harris)

MAXUSERS and NPROC are the SunOS 4.1.3 accessways to controlling

Look in /usr/share/sys/`arch -k`/KERNELNAME/param.c to see how this works.

Typically, just bumping MAXUSERS (as high as 256 or even more) in the
kernel config file is all you need to do.



PS on your aside question I think /usr/etc/tunefs does all that you need.

-- *** *** *** -- *** *** *** -- *** *** *** --

From: (Guy Harris)

Generally, in pre-SunOS-5.x systems, you adjust those parameters by
cranking up the "maxusers" value in the kernel configuration file.
However, the UFS file system will automatically allocate more inodes as
necessary in SunOS 4.1.1 and later (maybe 4.1 as well).

>As an aside, does Solaris 2.1 support the mtune, stune files and idconfig
>program for configuring the kernel? That would make things easier, as we
>can wait until the database is ported (should be soon) and then tune

No, I think it does that differently - it may well dynamically allocate
things such as system file table entries and inodes (probably *does*
dynamically allocate inodes; given that 4.1.x did, it'd be a bit silly
for 5.x not to...).

-- *** *** *** -- *** *** *** -- *** *** *** --

From: RichardT <>

You want to look in /sys/sun4/conf.common/param.c. *HOWEVER* the traditional
way to adjust this value is by increasing maxusers in the standard config
file in /sys/sun4/conf/<config>. nfile is calculated at compile time based
on the vaule of maxusers, and you almost certainly do not want to dink with


This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:38 CDT