SUMMARY: sizer command innaccurate?

From: <rem_at_MATH.AMS.ORG>
Date: Fri, 03 May 1996 08:18:30 -0400

Thanks to all those who replied. At least now I know the
kernel is set to what I wanted it to be. Now I'll start
to hunt down the process that forks off all the processes
which causes my original problem...

Special thanks to:

Kym Schwarz <schwarz_at_redbck.stl.dec.com>
"Miguel Mena (Digital UNIX Support Switzerland)" <migi_at_zuo.dec.com>
Hellebo Knut <Knut.Hellebo_at_nho.hydro.com>



I should have used dbx to check for maxusers in the running kernel.

# dbx -k /vmunix /dev/mem
dbx version 3.11.10
Type 'help' for help.

stopped at [thread_block:2046 ,0xfffffc00002a7298] Source not available

warning: Files compiled -g3: parameter values probably wrong
(dbx) p maxusers
128
(dbx)


 
Received on Fri May 03 1996 - 15:04:11 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:46 NZDT