From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: joshk@triplehelix.org, midian@ihme.org, hpa@zytor.com
Subject: Re: 2.6.5 pts problem
Date: 19 Apr 2004 01:52:09 -0400 [thread overview]
Message-ID: <1082353929.850.126.camel@cube> (raw)
>> As you see, pts is just growing, not using the old used numbers.
>
> The implementation was changed intentionally to make
> it that way. The numbers will only be recycled once we
> go over the max number of psuedoterminals, I think..
You can also recycle the numbers by rebooting.
That's what I do. :-/
(I can't be spending 10% of my disk on a giant wtmp
file. Also, I use the tty names for xterm titles now.
If they get too big, the GNOME taskbar button titles
get truncated.)
next reply other threads:[~2004-04-19 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 5:52 Albert Cahalan [this message]
2004-04-19 9:13 ` 2.6.5 pts problem Jorge Bernal (Koke)
-- strict thread matches above, loose matches on Subject: below --
2004-04-18 16:25 Markus Hästbacka
2004-04-18 21:48 ` Joshua Kwan
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=1082353929.850.126.camel@cube \
--to=albert@users.sf.net \
--cc=hpa@zytor.com \
--cc=joshk@triplehelix.org \
--cc=linux-kernel@vger.kernel.org \
--cc=midian@ihme.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