Version: 1.3.1 (using KDE KDE 3.2.1) Installed from: Debian testing/unstable Packages OS: Linux output of tty command is in the form /dev/pts/N When N is greater than 256 you can no longer use konsole (you open it but get no command prompt). The only way to continue using konsole is to reboot the system. Every time you open a konsole (or a xterm or the like) a new number is created. I know 256 is a not too low value; but for a laptop where you usually do not reboot the system (you put it to sleep) that limit is reached in a couple of days of "normal operation".
hmm, the pts numbers are released when you close xterm/konsole/whatever. That would be a bug in your kernel/glibc
ok, I suspected something like that. OTOH, would it be possible to increase that "limit" to a larger value. when my system reached that number, I could still use xterm w/o problems. Thanks for your attention. -- Kiko
I've just remembered having read something about pts's on lkml some time ago. I'm running kernel 2.6.4 and it results that since 2.6.4 pts numbers are reused like pid numbers. So, I guess konsole should allow that number to be greater than 8 bits. Thanks again.
I just stressed my system a bit and found that /dev/pts indeed only allows 255 entries. more than 230 xterms are forbidden by X it seems - at least new xterms I can't open because of "too many X clients" :) I then opened another 40 screen sessions and those open /dev/ttyp.. when /dev/pts runs out of numbers. I'm not sure this should be supported by konsole though as running out of /dev/pts should be a pretty rare situation caused by a different bug. You should check which application holds your /dev/pts inodes open
what architecture do you use? (*Intel? PowerPC?) Ciao, Marcus
On 22/03/2004 at 20:18, Marcus Meissner wrote: > what architecture do you use? (*Intel? PowerPC?) PowerPC. I use i386 at home and at work. Right now I'm out and can only test it with my laptop (iBook, ppc). I will try to reproduce it on i386 tomorrow. Both with ppc and with i386 I'm running vanilla 2.6.4 kernel. Thanks
this is a powerpc glibc problem (I have also seen it on my PPC machine). This has been fixed in the GLIBC CVS. Workaround is to compile the affected application with large file support.
On 22/03/2004 at 20:56, Marcus Meissner wrote: > this is a powerpc glibc problem (I have also seen it on my PPC machine). > This has been fixed in the GLIBC CVS. > > Workaround is to compile the affected application with large file support. Ah!, then sorry for bothering you all. Many thanks to everyone for responding and for this information.
not a KDE bug then :)