2. You should check /dev/pts and make sure all the links are there.
3. Do not modify maxusers, it has nothing to do with the maximum
number of users (thus the name?) but is used to change numerous
calculations normally done based on the amount of memory available.
Casper Dik had a recent post emphasizing many misunderstandings, about
the /etc/system variable settings.
4. Issuing the command "devlinks" will create the entries in /dev/pts
without requiring a reboot. I looked at other commands, like "pmadm"
and "ports", to see if there was something I could do to bring them up on
the fly. I think it's possible but I didn't find it.
5. I opened up enough terminals to make sure I had increased the
number of pty's after the reboot. (If I had done this the first time,
I wouldn't have sent the initial message to the list.) By doing this
on one of my NCD Xterms and then checking later, I also discovered
that the reason I was repeatedly running out of pty's was that the
process aren't always being killed when users log off the Xterms due
to problems with CDE.
No one mentioned my misspelling "maximum"; thank you.
====================================================================
Setting pt_cnt=n should be all you need to do.
Of course, you have to reboot the machine for the new
kernel parameters to take affect.
Sender: "Mark Belanger" <mark_belanger@ltx.com>
====================================================================
From: "K.Ravi" <RAVKRISH.IN.oracle.com.ofcmail@in.oracle.com>
If you have done a 'boot -r' after modifying /etc/system, you should
have the device entries in /dev/pts. See if you have files from 0 to
199 in t his directory.
====================================================================
From: Casper Dik <casper@holland.Sun.COM>
Did you remember to "boot -r" after changing pt_cnt?
Try ls /dev/pts and check if the links are all there.
BTW, it's typically not a good idea to set maxusers (it has nothing to
do with the number of users allowed at the same time)
====================================================================
Joel Lee <jlee@thomas.com> | Network Administrator/System Programmer
( I found this very helpful.)
First of all, did you reboot ? If you are not sure, run
echo 'pt_cnt/X' | adb -k /dev/ksyms /dev/mem, this will tell you
what's the value your kernel is holding.
When I tried this
physmem 5df0
pt_cnt:
pt_cnt: c8
which told me my pt_cnt was at 200
====================================================================
Similar advice also from:
"Brion Leary" <brion@dia.state.ma.us>
Kris Briscoe <brisco_k@adm-srv.sat.mot.com>
seeger@cise.ufl.edu (Charles Seeger)
"Mark Belanger" <mark_belanger@ltx.com>
mbaker@macquarie.com.au (Maryanne Baker)
-- Josh Kuperman josh@cs.albany.edu Unix System Administrator Dept. of Computer Science University at Albany (518) 442-5682 1400 Washington Avenue (518) 442-5638 (fax) Albany, NY 12222