Messages in this thread | | | From | Andrzej Krzysztofowicz <> | Subject | PTS alocation problem with 2.6.4/2.6.5 | Date | Tue, 6 Apr 2004 00:53:06 +0200 (CEST) |
| |
I noticed serious problem with PTS alocation on kernels 2.6.4 and 2.6.5: It seems that once alocated /dev/pts entries are never reused, leading to pty alocation errors. The testing system is fully compiled with kernel 2.2.x headers (including glibc), but informations from my coleagues using systems compiled on 2.4/2.6 headers seems to behave similarily. The testcase and used kernel configuration are shown below. Kernel 2.6.3 does not have this problem. Is it bug or feature (and I am doing sth wrong) ?
NOTE: I realize that my glibc does not support minors > 255, so no more pts-es is available, but problem is leakage of _free_ pts-es.
[ankry@green SPECS]$ for a in $(seq 4);do ssh -t remote tty;done /dev/pts/253 Connection to remote closed. /dev/pts/254 Connection to remote closed. /dev/pts/255 Connection to remote closed. not a tty Connection to remote closed. [ankry@green SPECS]$ ssh remote cat /proc/sys/kernel/pty/{max,nr} 2048 1 $ ssh olimp ls /dev/pts 1
.config tested (selected entries)
CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=2048
or
CONFIG_UNIX98_PTYS=y # CONFIG_LEGACY_PTYS is not set
(full .config available on request)
-- ======================================================================= Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl phone (48)(58) 347 14 61 Faculty of Applied Phys. & Math., Gdansk University of Technology - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |