From owner-freebsd-questions@FreeBSD.ORG Thu Nov 15 20:02:15 2007 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9755016A417 for ; Thu, 15 Nov 2007 20:02:15 +0000 (UTC) (envelope-from ccowart@rescomp.berkeley.edu) Received: from hal.rescomp.berkeley.edu (hal.Rescomp.Berkeley.EDU [169.229.70.150]) by mx1.freebsd.org (Postfix) with ESMTP id 81A3613C447 for ; Thu, 15 Nov 2007 20:02:15 +0000 (UTC) (envelope-from ccowart@rescomp.berkeley.edu) Received: by hal.rescomp.berkeley.edu (Postfix, from userid 1225) id 364803C04B8; Thu, 15 Nov 2007 12:02:15 -0800 (PST) Date: Thu, 15 Nov 2007 12:02:15 -0800 From: Christopher Cowart To: questions@freebsd.org Message-ID: <20071115200215.GF43532@hal.rescomp.berkeley.edu> Mail-Followup-To: questions@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="U5yJ31ax00IavOwq" Content-Disposition: inline Organization: RSSP-IT, UC Berkeley User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: Kernel pty limit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2007 20:02:15 -0000 --U5yJ31ax00IavOwq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, I went to open up a new shell to our login server (recently rebuilt from Debian to FreeBSD) and found problems allocating a new pty. With a 256-pty limit, I'm surprised more people haven't had this problem. With team of 8 SysAdmins, each leaving about 30 windows open in screen sessions, 256 starts feeling a bit claustrophobic.=20 I found a questions thread from January 2006 and these PRs: standards/90896: not enough PTYs in the FreeBSD kern/25866: [patch] more than 256 ptys, up to 1302 ptys. The latter appears to have been kicking around since FreeBSD 4.3 (still open).=20 What can I do to help get that limit raised? Does anyone have a patch against 6.2? If not, would anyone be interested in writing one? Thanks for any help, --=20 Chris Cowart Lead Systems Administrator Network & Infrastructure Services, RSSP-IT UC Berkeley --U5yJ31ax00IavOwq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iQIVAwUBRzylxiPHEDszU3zYAQLamhAAuTDINSvRwbbHmez4onsFbkvluLYLM3C7 sWlM1N7G5uNayQtM3Yov4WOhRGsfcG92k9e/f/fTo2biueff/3A5ndO+t2n3Xf5Y IBhe+VxFNpCVo+DMThNvaNcxFILv0lUi/qRfzoFYGhPaPJ1Msem8dOn/VV1QIGvn Gw5ENDXEs9BHV6ucIVObxfHZafU34JkZznLtqZFLJ/Cxk6b4tZat0oqHO+s5/EL4 CuqlKkXGqmvMHP8+F+yrx0Djvj4mUx6SuOcLmgvL8WIIbpAKkRrz2n7cTIOn7Dyy fEbLMY68CGpzAGOqg5H51V5Sf9IP5Ttq9XlT/FNF+E4t+xaEhkuxT5xSFIG/20ou gn6mfsIuGBxvHWTsMo9oAWVsg5w1yWRDlu8M8gFHsBrhZFWrgmh4j8KvqVLu7N6E jpdZJRlqv0cZFdZjYxH3pjk6YI4j6554vNVbIlGSpNfH1qeS6TRDCdU33jULzHRl EkNg2vb1y5PVPVmIdZaDvV5qpi73kVNhSsAuqd1g8q8NWBRl9gQpRr3Bbm55veH6 F6/pwDq81UsxiiQqi4siKpcnNfCvUR9isv0x6wIOzJ6vqfqGkmQaUw2CrJ9ev9qF 6K53TVdCkjrBVDPRhZTKvqiyAbKw/QpfQSXWE8NjlXyjZvimesRxASoOKJuJqgPk +e1maBR29Ik= =q8Dl -----END PGP SIGNATURE----- --U5yJ31ax00IavOwq--