From: Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl>
To: akpm@osdl.org (Andrew Morton)
Cc: ankry@green.mif.pg.gda.pl (Andrzej Krzysztofowicz),
linux-kernel@vger.kernel.org
Subject: Re: PTS alocation problem with 2.6.4/2.6.5
Date: Tue, 6 Apr 2004 07:11:51 +0200 (CEST) [thread overview]
Message-ID: <200404060511.i365Bpie022092@green.mif.pg.gda.pl> (raw)
In-Reply-To: <20040405165957.5f8ab8dc.akpm@osdl.org> from "Andrew Morton" at Apr 05, 2004 04:59:57 PM
Andrew Morton wrote:
>
> Andrzej Krzysztofowicz <ankry@green.mif.pg.gda.pl> wrote:
> >
> > 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) ?
>
> You need a glibc upgrade - we broke things for really old glibc's. We're
> (slowly) working on fixing it up.
Hmmm, which version is enough ?
I use glibc-2.2.5, but people using glibc-2.3.3 snapshot, dated 20040101
also have the same problem...
--
=======================================================================
Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl
phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math., Gdansk University of Technology
next prev parent reply other threads:[~2004-04-06 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 22:53 Andrzej Krzysztofowicz
2004-04-05 23:59 ` Andrew Morton
2004-04-06 5:11 ` Andrzej Krzysztofowicz [this message]
2004-04-06 17:55 ` Jamie Lokier
2004-04-06 18:16 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200404060511.i365Bpie022092@green.mif.pg.gda.pl \
--to=ankry@green.mif.pg.gda.pl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®