by Ming P » Wed, 17 Apr 1996 04:00:00
I have a problem in a machine here that when there are more
than 40 telnet sessions, the system will give out the following
error message:
telnetd: open /dev/ptmx no such device.
Seems like telnet have max out the ptmx pusedo device and I could
not find any documentation on how to increase it.
Any idea is greatly appreciated.
Thanks
by Ruben Martine » Thu, 18 Apr 1996 04:00:00
> I have a problem in a machine here that when there are more
> than 40 telnet sessions, the system will give out the following
> error message:
> telnetd: open /dev/ptmx no such device.
> Seems like telnet have max out the ptmx pusedo device and I could
> not find any documentation on how to increase it.
> Any idea is greatly appreciated.
> Thanks
by Walter Gree » Thu, 18 Apr 1996 04:00:00
As root do the following (# indicates a root prompt)...
# adb -k /kernel/unix /dev/mem
# pt_cnt/D
# $q
# vi /etc/system
set pt_cnt=75
# reboot -- -r
Cheers,
-Walter
> I have a problem in a machine here that when there are more
> than 40 telnet sessions, the system will give out the following
> error message:
> telnetd: open /dev/ptmx no such device.
> Seems like telnet have max out the ptmx pusedo device and I could
> not find any documentation on how to increase it.
> Any idea is greatly appreciated.
> Thanks
1. kernel: grow_inodes: inode-max limit reached
Hello everybody,
I have the problem that every night at 00:00 my linux kernel produces
the message: "kernel: grow_inodes: inode-max limit reached"
I know how to read and modify the kernel parameters with the help
of the /proc filesystem and I am also aware of the fact that
a cron job could started at 00:00 could be responible (Although
I wasn't able to identify it)
But my question aims at another direction:
On the net I found a text
(http://linux.web.cern.ch/linux/lsr/doc/kernel/proc.txt)
where you can read, that file-handels and inode-handles are dynamically
allocated by
the kernel but not freed again?
Does somebody know whether this is on purpose for efficiency or
whatever,
or if it is a bug?
Secondly - and even more important for me - if the number of used inodes
is bigger then inode-max, does that mean that the system will no longer
work reliable, or is this pre shrink method mentioned in
(http://linux.web.cern.ch/linux/lsr/doc/kernel/proc.txt) something that
will work very well?
By the way, I can increase the values of inode-max and file-max. But are
there any upper limits for these values I cannot go beyond?
Thanks in advance for help or pointers...
Thanks in advance,
Markus Jochim
2. Share modem, ISDN and cable modem 12048
3. Boot problem "VFS: file-max limit 8192 reached" anyone help?
5. Apache reached Max child limit
7. Using accept() when max FD limit has been reached
8. newbie needs help setting up modem to work on linux with IBM Thinkpad i 1411
9. grow inodes: inode-max limit reached error.
10. inode overflow; c queue max run limit reached
11. LinuxPPC2000 Kernal Panic: Unable to mount ext2 max limit reached..Please Help!
13. grow-inodes: inode-max limit reached