From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: hpa@zytor.com, cloos@jhcloos.com, root@chaos.analogic.com,
nuno@itsari.org
Subject: Re: something funny about tty's on 2.6.4-rc1-mm1
Date: 02 Mar 2004 14:04:44 -0500 [thread overview]
Message-ID: <1078254284.2232.385.camel@cube> (raw)
> As RBJ said, ptys are now recycled in pid-like fashion,
> which means numbers won't be reused until wraparound
> happens. This is good for security/fault tolerance,
> at least to some minor degree.
Ouch. It's bad for display and bad for typing.
What is easier to type?
ps -t pts/6
ps -t pts/1014962
(and yes, I really type these -- I don't have a
third hand to operate the mouse simultaneously)
What looks better?
UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
albert 3339 2114 0 771 1684 0 Feb26 pts/6 00:00:00 bash
albert 3149 2514 0 771 1684 0 Feb26 pts/1004922 00:00:00 bash
albert 3835 2164 0 771 1684 0 Feb26 pts/8 00:00:00 bash
albert 4136 3114 0 771 1684 0 Feb26 pts/1013866 00:00:00 bash
albert 4739 2119 0 771 1684 0 Feb26 pts/9 00:00:00 bash
Better way:
Have a soft limit, initially set at 99. When 2/3 of
the ptys are in use, increase the soft limit to 999,
then to 9999, 99999, and finally to 999999.
This way, a plain 1-person desktop user would never
have a pty name longer than pts/99 and an insanely
busy server could go as high as needed.
next reply other threads:[~2004-03-02 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-02 19:04 Albert Cahalan [this message]
2004-03-02 19:54 ` something funny about tty's on 2.6.4-rc1-mm1 H. Peter Anvin
2004-03-02 22:46 ` Edgar Toernig
2004-03-02 23:59 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-03-03 4:12 Albert Cahalan
2004-03-01 18:45 Nuno Monteiro
2004-03-01 19:09 ` Richard B. Johnson
2004-03-02 5:47 ` H. Peter Anvin
2004-03-02 14:52 ` James H. Cloos Jr.
2004-03-02 15:02 ` Richard B. Johnson
2004-03-02 17:47 ` James H. Cloos Jr.
2004-03-02 16:54 ` H. Peter Anvin
2004-03-02 22:08 ` Andrew Morton
2004-03-03 2:29 ` H. Peter Anvin
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=1078254284.2232.385.camel@cube \
--to=albert@users.sf.net \
--cc=cloos@jhcloos.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno@itsari.org \
--cc=root@chaos.analogic.com \
/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