From owner-freebsd-current@FreeBSD.ORG Tue Sep 26 11:39:18 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93A0D16A412 for ; Tue, 26 Sep 2006 11:39:18 +0000 (UTC) (envelope-from jrh29@alumni.cwru.edu) Received: from eastrmmtao05.cox.net (eastrmmtao05.cox.net [68.230.240.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4705743DAD for ; Tue, 26 Sep 2006 11:39:13 +0000 (GMT) (envelope-from jrh29@alumni.cwru.edu) Received: from eastrmimpo01.cox.net ([68.1.16.119]) by eastrmmtao05.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060926113912.GIGQ7951.eastrmmtao05.cox.net@eastrmimpo01.cox.net> for ; Tue, 26 Sep 2006 07:39:12 -0400 Received: from [192.168.1.100] ([68.98.142.45]) by eastrmimpo01.cox.net with bizsmtp id Szf81V00E0yyTD80000000 Tue, 26 Sep 2006 07:39:08 -0400 Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <20060926111452.J91466@godot.imp.ch> References: <20060926111452.J91466@godot.imp.ch> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <0C4B0125-11AA-4BDB-A4E3-163A6194AB68@alumni.cwru.edu> Content-Transfer-Encoding: 7bit From: Justin Hibbits Date: Tue, 26 Sep 2006 07:39:11 -0400 To: current@freebsd.org X-Mailer: Apple Mail (2.750) Cc: Subject: Re: What do you think ?: How should pseundo terminals behave ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Sep 2006 11:39:18 -0000 On Sep 26, 2006, at 05:33 , Martin Blapp wrote: > So how should ptys behave ? > > 1.) Block until the tty is really opened again and there is > a master available again. Then write to the freshly opened > pty. (not easy to do) > > 2.) Block forever since the tty will not be reopened anymore since > we leak ptys. > > 3.) Detect that there is no master around anymore and > return ENXIO: > > # echo "BLUBBER" > /dev/ttypX > # /dev/ttypX: Device not configured > > (easy to do, i've got a fix. IMHO this is the best thing to > do. This allows fast error recovery in case the master > has been gone away) > > 4.) Keep the current behaviour, leak terminals or panic. > > (the simplest thing to do. Let's keep the bugs) > > Please vote for any of those choice. Thank you for your > participation. > > Martin I vote #3, it makes the most sense. - Justin