From owner-freebsd-hackers@FreeBSD.ORG Tue Oct 2 12:58:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68EB716A468 for ; Tue, 2 Oct 2007 12:58:52 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id E543613C4B0 for ; Tue, 2 Oct 2007 12:58:51 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by mu-out-0910.google.com with SMTP id w9so5146169mue for ; Tue, 02 Oct 2007 05:58:50 -0700 (PDT) Received: by 10.82.111.8 with SMTP id j8mr7558730buc.1191329930215; Tue, 02 Oct 2007 05:58:50 -0700 (PDT) Received: by 10.82.148.14 with HTTP; Tue, 2 Oct 2007 05:58:49 -0700 (PDT) Message-ID: Date: Tue, 2 Oct 2007 15:58:49 +0300 From: "Vlad GALU" To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" In-Reply-To: <86sl4twuf1.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <001f01c80407$1358d490$b6db87d4@multiplay.co.uk> <012101c804e5$efa7e9c0$b6db87d4@multiplay.co.uk> <86abr1yb68.fsf@ds4.des.no> <86641pyanc.fsf@ds4.des.no> <86wsu5wuz3.fsf@ds4.des.no> <86sl4twuf1.fsf@ds4.des.no> Cc: freebsd-hackers@freebsd.org, Steven Hartland , freebsd-stable@freebsd.org, gepu@flow.rdsnet.ro Subject: Re: How to enable more than 256 pty's? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2007 12:58:52 -0000 On 10/2/07, Dag-Erling Sm=F8rgrav wrote: > "Vlad GALU" writes: > > Dag-Erling Sm=F8rgrav writes: > > > "Vlad GALU" writes: > > > > The symptoms were exhibited even with rev. 1.16. I've CC'ed him so > > > > he can catch up with the thread. > > > Which symptoms? I can no longer reproduce the hang-on-close bug. > > Strangely enough, me neither. In his case, allocated pts' wouldn't get > > deallocated once the sessions ended. > > Wouldn't get deallocated right away, or wouldn't get deallocated at all? > Apparently, it is not unusual for pts reclamation to be delayed a bit by > a non-zero refcnt. > As per my other mail, they wouldn't get deallocated at all. They still show up in /dev/pts/ even after closing, and the next integer index is picked up upon the next terminal creation. > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > --=20 If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it.