My previous posting:
|>Greetings -
|>
|>All of my attempts to raise CHILD_MAX (visible via getconf CHILD_MAX) from
|>64 have been unsuccessful. I've modified <sys/syslimits.h> altering the 64
|>and making it 256, I've modified param.c, I've raised maxuprc in
|>/sys/conf/<SYSNAME>, etc... after each modification attempt I've rebuilt
|>the kernel and moved the new kernel to / and rebooted. Still
|>getconf CHILD_MAX (and _POSIX_CHILD_MAX) remain unchanged at 64 and 6
|>respectively. Any other ideas? Is this a v3.0 limitation?
|>
|>TIA Summary pending responses.
|>
Yes, I know I can increase the number of processes per user, but the CHILD_MAX
parameter is the sticking point.
The responses thus far have been identical to editing the configuration file
during kernel rebuild and manually adding/updating the maxuprc value. The
responses have been to edit /etc/sysconfigtab or to create /etc/proc.stanza
either of which is to include:
proc:
max-proc-per-user = 256
Then (if file edited was proc.stanza) sysconfigdb -f /etc/proc.stanza proc
should be typed, to include that in the database. Then reboot.
This still doesn't update the CHILD_MAX parameter though. According to the
getconf(1) man page the configuration variables `contain the minimum values
met throughout all portions of the system.' This may mean that this value
is the smallest maximum anything in the system relies on. Does anyone
really know? My v3.2 systems all have a larger CHILD_MAX than my v3.0
systems. Any ideas? (it is not a difference in <sys/syslimits.h> between
v3.0 and v3.2)
TIA Summary pending additional responses.
Randy M. Hayman
haymanr_at_icefog.alaska.edu
Received on Fri Jun 23 1995 - 03:25:23 NZST