Thanks to all the people that sent a response to my question. They are
as follows:
Bryan.Lavelle_at_digital.com
Kris.Chandrasekhar_at_digital.com
Joel_Gallun/US/DCI_at_discovery.com
C.Ruhnke <i769646_at_smrs013a.mdc.com
harisharora_at_hotmail.com
Simon.Millard_at_barclays.co.uk
crossmd_at_mh.uk.sbphrd.com
alf_at_northpower.com.au
tpb_at_doctor.zk3.dec.com
rdbowma_at_tsi.clemson.edu
dvigneau_at_heron.anselm.edu
mcrowley_at_mtholyoke.edu
gguethlein_at_giantofmarylandcom
A few people were under the same impression as my self that maxuprc
was a statement that could be added to the kernel config file and when
the kernel was rebuilt then used to boot the system it would take
affect. Well, as many people pointed out that is not the way to do it.
There are a few ways to do this, the easiest by far is the utility
called dxkerneltuner, you make the required change and reboot the
system (try it you'll like it).
The second easiest but more disastrous if a mistake is made and then
saved is to directly vi the /etc/sysconfigtab file and add the
following to the "END" of the file:
:proc
max-proc-per-user = 512 (or what ever number you want)
Then reboot the system.
The third way is to vi a file with an arbitrary name we'll call it
"wilma" (this is called a stanza file) and add the following to it:
:proc
max-proc-per-user = 512 (or what ever number you want)
then do the following to input the stanza file info into the
/etc/sysconfigtab file
sysconfigdb -a -f wilma proc
This third way is the safe way make changes to the /etc/sysconfigtab
file.
Gary Beckett
systems Analyst
Royal BC Museum
675 Belleville St
Victoria, BC
V8W 9W2
Ph# (250)387-2445
Fax# (250)387-5360
****************************************************************
"Let the words be yours, I'm done with mine..."
- john p barlow
****************************************************************
Received on Thu Dec 31 1998 - 17:20:10 NZDT