From owner-freebsd-current@FreeBSD.ORG Tue Sep 23 21:25:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0602E10656AF for ; Tue, 23 Sep 2008 21:25:09 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp2a.orange.fr (smtp2a.orange.fr [80.12.242.139]) by mx1.freebsd.org (Postfix) with ESMTP id C2B578FC19 for ; Tue, 23 Sep 2008 21:25:01 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2a11.orange.fr (SMTP Server) with ESMTP id EB7D9700008D; Tue, 23 Sep 2008 23:25:00 +0200 (CEST) Received: from localhost (AToulouse-156-1-77-238.w86-196.abo.wanadoo.fr [86.196.164.238]) by mwinf2a11.orange.fr (SMTP Server) with ESMTP id 3E44A7000088; Tue, 23 Sep 2008 23:25:00 +0200 (CEST) X-ME-UUID: 20080923212500255.3E44A7000088@mwinf2a11.orange.fr Message-ID: <48D95EAB.6070300@orange.fr> Date: Tue, 23 Sep 2008 23:24:59 +0200 From: Claude Buisson User-Agent: Thunderbird 2.0.0.16 (X11/20080727) MIME-Version: 1.0 To: Ed Schouten References: <48D81DEE.4070103@orange.fr> <20080923172149.GN81522@hoeg.nl> In-Reply-To: <20080923172149.GN81522@hoeg.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: Problem telneting to a new -current 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, 23 Sep 2008 21:25:09 -0000 Ed Schouten wrote: > Hello Claude, > > Sorry for letting you wait this long. I was in a rush this afternoon, so > I couldn't fix it for you right away. > No problem, ssh worked fine.. > It turns out there was a small inconsistency between the old and the new > pseudo-terminal driver, which caused telnetd to exit prematurely. The > new pts(4) driver did not track any state on if it had been used > already. This meant that when select() in telnetd would be called right > before the child processes had opened the TTY device node, it would just > assume that the session was already finished. > > I've committed a fix to SVN (183308), which should removes this > inconsistency. I assumed it wouldn't be a very important problem, > because most of the PTY consumers already use the openpty() routine, > which already opens the TTY device node unconditionally. It turns out > some things went bad after all. Could you try updating to the latest > sources to see if the problem is solved now? > > I've also spotted another `bug' in telnetd. If I log in to telnetd, I > see the following message appear in dmesg: > > pid 2362 (telnetd) is using legacy pty devices > > This means telnetd has its own PTY allocation routines, instead of using > posix_openpt(2) or openpty(3). I've attached a patch that converts > telnetd to openpty(3). I'll see if I can get this patch or something > similar integrated. > Yes, I got this same message > Thanks for reporting the issue! > > cvsup done, will try the new source and the telnetd patch, and report as soon as possible. Regards Claude Buisson