From owner-freebsd-ports@FreeBSD.ORG Mon Mar 25 10:01:13 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8E10CCAC for ; Mon, 25 Mar 2013 10:01:13 +0000 (UTC) (envelope-from coco@executive-computing.de) Received: from mail.moehre.org (mail.moehre.org [195.96.35.7]) by mx1.freebsd.org (Postfix) with ESMTP id 53B31C16 for ; Mon, 25 Mar 2013 10:01:12 +0000 (UTC) Received: from mail.moehre.org (unknown [195.96.35.7]) by mail.moehre.org (Postfix) with ESMTP id 7752A8B143C; Mon, 25 Mar 2013 11:01:11 +0100 (CET) X-Spam-Flag: NO X-Spam-Score: -100.964 X-Spam-Level: X-Spam-Status: No, score=-100.964 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, AWL=0.036, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mail.moehre.org ([195.96.35.7]) by mail.moehre.org (mail.moehre.org [195.96.35.7]) (amavisd-new, port 10024) with ESMTP id WOklqccFwQHQ; Mon, 25 Mar 2013 11:01:09 +0100 (CET) Received: from [192.168.100.30] (p54B0A677.dip.t-dialin.net [84.176.166.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: coco@executive-computing.de) by mail.moehre.org (Postfix) with ESMTPSA id DBE6F8B143B; Mon, 25 Mar 2013 11:01:09 +0100 (CET) Message-ID: <51502087.40108@executive-computing.de> Date: Mon, 25 Mar 2013 11:01:43 +0100 From: Marco Steinbach User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: eugene@wdc.spb.ru Subject: Re: cannot open tty-output References: <514F56BF.5040805@home.wdc.spb.ru> <20130324215847.2243e4dc@bsd64.grem.de> <514F8E36.3010606@executive-computing.de> <51501192.30303@home.wdc.spb.ru> In-Reply-To: <51501192.30303@home.wdc.spb.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2013 10:01:13 -0000 Eugene V. Boontseff wrote on 25.03.2013 09:57: > On 25.03.2013 03:37, Marco Steinbach wrote: >> Michael Gmelin schrieb: >>> On Sun, 24 Mar 2013 23:40:47 +0400 >>> "Eugene V. Boontseff" wrote: >>> >>>> *Marco Steinbach wrote: >>>> * >>>>> Hi, >>>>> >>>>> after installing dialog4ports, I'm getting the following behaviour >>>>> on each 8.3-STABLE I tried: >>>>> >>>>> # jexec /bin/tcsh >>>>> # cd >>>>> # make config >>>>> >>>>> cannot open tty-output >>>>> ===> Options unchanged >>>>> # >>>>> >>>>> Regardless, if I'm logged in on the console or connect to the host >>>>> via ssh. >>>>> >>>>> >>>>> I've also tried on 8.4-BETA1 (r248617), but got the same behaviour. >>>>> >>>>> Anyone else experiencing this ? >>>> Yes, I have also experienced this. >>>> 8.3-STABLE r244863 >>>> Only if i do a "make config" in a jail. >>>> Outside the jail all goes well. >>>>> MfG CoCo >>> >>> This problem doesn't exist in 9.1. On 8 it only happens when you >>> jexeced into the jail (ssh should be ok). As a workaround you can run >>> tmux (sysutils/tmux) within your jail and install ports from within the >>> terminal multiplexer (screen will do as well, but is also heavier). >>> >> >> dialog4ports(1) uses stdout for passing back results, where the former >> dialog(1) used stderr. I reverted the new behaviour back to the >> previous one, which fixed the problem for me. I don't know about >> other implications, though. >> >> Ilya (author of dialog4ports) is aware of the problem and having a >> look at it. >> >> I'm glad that other people are running into this, also. I was >> beginning to think, that there's something fundamentally wrong with >> the way our 8.x jails are configured. > What could it be? I configure jail with ezjail. Nothing special.. :-) > >> MfG CoCo > > Same here. With and without ezjail, same behaviour on all 8.x machines I tried. Using a serial console on a 9.1 machine yields the same behaviour when jexec is used, while there's no error when connected per ssh. MfG CoCo