When I asked why max-procs-per-user in my /etc/sysconfigtab wouldn't exceed 267
users even though I had specified 512 and modified the sysconfigtab properly
with sysconfigdb. Martin Moore of DEC UNIX Support, offered this clear
explanation:
*********************
I'll bet your maxusers is set to 32 (the default). Prior to 4.0 you can
only change this in the kernel configuration file, meaning you have to
rebuild the kernel.
The reason is that the max-procs-per-user is pegged by the maximum number
of total process in the system minus some delta. (Obviously one user can't
have more processes than the entire system allows.) This number is computed
as maxusers*8+20, or 276 when maxusers=32.
Martin J. Moore martin_at_alf.dec.com
****************************************
Paul Henderson, also of DEC, offered the same answer and went on:
FYI, in V4.0 and later, a tool is included called dxkerneltuner that
offers a graphical front end to change kernel parameters, both to the
running kernel and /etc/sysconfigtab.
Paul Henderson henderson_at_unx.dec.com
****************************************
My original message:
> I have used sysconfigdb to change 2 proc parameters and 2 vm parameters (in
> hopes of assuaging Netscape Enterprise Server, which after a few hours fails on
> HTTP GETs with "error opening buffer from /path/doc : not enough space").
>
> The sysconfigdb command completed successfully and updated /etc/sysconfigtab.
> Howver, after rebooting and confirming the changes with "sysconfig -q proc",
> one parameter, max-procs-per-user, as 267, though the table shows that I set
> it to 512. Why would this be?
>
> Thanks for any thoughts. I don't think this one parameter is life or death; the
> others were the most interesting (proc: max-threads-per-user; vm:
> vm-mapentries; vm-vpagemax). However, it would be good to understand more about
> how all this works!
Received on Thu Feb 13 1997 - 20:11:24 NZDT